Database Info

[RECOVERY] Reverting to original(STOCK) recovery

WARNING: IN THE EVENT THAT ANYTHING GOES WRONG, I WILL NOT BE HELD ACCOUNTABLE. I CANNOT STRESS THIS ENOUGH!!!
EDIT: I FORGOT, BEFORE CHANGING RECOVERY OR DOING ANYTHING, ALWAYS DO A NANDROID BACKUP!!!
If you have flashed a custom recovery (clockwork, j_r0dd, etc.) but you want to
1) accept OTA updates but cant do so with the custom recovery
2) send your phone for repair and not void your warranty
3) or UNROOT YOUR PHONE,
it should be easy to revert back to your stock recovery that came with your phone.
NOTE: THIS PROCEDURE WILL ONLY WORK IF THERE IS AN AVAILABLE OTA UPDATE FOR YOUR PHONE!!!
YOU WILL HAVE TO RE-ROOT YOUR PHONE IF YOU WANT ROOT ACCESS AFTER UPDATING! DO NOT RE-ROOT IF YOUR PHONE IS TO BE SENT FOR REPAIR!
Step 1) Download the OTA update. (I have a uploaded a sample update zip at
www . sidsoftinc . com / Blur_Version.0.3.9.MB300.Retail.en.03.zip
*remove the spaces)
Step 2) On completion, the phone should reboot and enter recovery mode, using the custom recovery to update. However, this should fail as most custom recoveries prevent original updates. Note the location of the downloaded update (likely at /cache)
Step 3) Power down the phone and enter into recovery mode manually
Step 4) Using ADB, pull the folder containing the update zip to your computer
Code:
adb pull /**storedlocation**/**nameoftheupdate**.zip update.zip
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Step 6) Open up the adb shell and flash the new recovery (recommended)
Code:
adb shell
su
flash_image recovery recovery.img
or you can place it in /system and it will be auto-flashed (not recommended)
Code:
adb push recovery.img /system/recovery.img
Step 7 (if possible) Make it permanent by deleting the custom recovery in /system
Code:
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Step 8) Reboot the phone and if you see a triangle warning sign, reboot your phone again. You should see your homescreen before it reboots to install the update again. This time, the original recovery will be used.
Once finished, your phone will be upgraded, unrooted and your applications and data will still be retained.
If you wish to install your previously used custom rom again, you must flash the custom recovery and install the rom, again
If I made a mistake, please do inform me. Thank you

I'm trying to do this for the Tmo G2 and I have reverted using another technique but the clockworkmod is still there. I thought it would get removed!
I have no idea how to get rid of it. Can you give me alittle help?

Did your clockworkmod recovery flash itself into your nv ram. If so then no one can help you there. If you have an ota update and pulled it to your pc, send me a coy and I'll see if I can help you. If you can, send me your ota update zip to [email protected].
Sent from my Motorola Backflip using the XDA App

I'm honestly unsure if it flashed to the nv-ram. Possibly, basically if I do a system boot (power +vol down) and select recovery, it will load the HTC green text with white background then go into clockword recovery. I'm not exactly sure why it still does this.
I used the method on this FORUM THREAD to un-root and get back to stock (using the available files there and method 1-a). I'm just unsure why the clockwork recovery is still there. I'm hoping I can still get back to stock recovery. Possibly I just need to flash the stock recovery.img??
Also, I had some troubles initially with ADB, which is why I used the VISIONary method of rooting. I'd love to try out the gfree method since I believe my ADB is working correctly now and test out some other roms to see what I like the most.

I know you are probably in a different time zone that is way ahead of mine........but can't I just reflash the stock or update ota recovery.img in fastboot mode.......OR is this a bad Idea???

Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App

siidheesh said:
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
Click to expand...
Click to collapse
I tried flashing the stock recovery but I'm not sure why it didn't work, I had hboot and flash_image. I used the adb shell way as well. It gave me error in partitions or whatever. I don't know what to do.

do you have Blur_Version.0.3.10.MB300.Retail.en.03.sbf file?

I dont happen to have that file, but i do have Blur_Version.0.3.9.MB300.Retail.en.03.zip
if you need it.

Cockwork Mod
I'm pretty green so this may sound really dumb, but can you flash sbf files to your phone via Clockwork Mod, or does it have to be done via RSD Lite. I cannot get RSD to recognize my device in 4.7 or 4.8. Please help.

do you have a stock image for the huawei ascend for cricket or does anyone here have it?

Unrooting......
I download the RECOVERY file you supplied (thank you)
"Blur_Version.0.3.9.MB300.Retail.en.03.zip"
If I reboot into Recovery and just flashed that zip file, would it work that way to unroot?

Provided you are flashing on a MOTOROLA BACKFLIP, yes. However, you might want to flash the AT&T 2.1 update for the backflip instead, if you reside in the US. Flashing back any official firmware unroots your phone

I'm looking to root and unlock my AT&F Motorola Backflip (MB300).. Any suggestions?
Sent from my NexusHD2 using Tapatalk

OTA for Samsung Galaxy Ace is a CFG file, not ZIP
Hello,
Just for interest, I received an OTA for my Samsung Galaxy Ace but it didn't come as a ZIP file - it came as a CFG file (which is not a ZIP, but actually a proprietary package - which I can't remember the name right now).
However, I did find the stock recovery elsewhere in this forum, and I installed it. But that wasn't enough for the OTA to be installed - it still fails.

Corrupted?
siidheesh said:
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Click to expand...
Click to collapse
I can't find it. I have an Alcatel Pop C1 4015X. Help?

Trying to unroot Xperia Z2
I am trying to unroot using update files from the Sony Xperia Companion. I found the update files (I think). I used Flashtool to decrypt the FILESET, but there is no recovery.img in the decrypted folder. The folder I decrypted is in Xperia Companion/Sony Mobile Update Engine/localstorage/db/13740270 and that is the only folder that has decryptable files. They are named FILE_8977018 and similar before decryption and various .sin .ta files (examples auto-boot.ta, cust-reset.ta, simlock.ta). Am I using the right decryption to get the recovery.img?

[Q]How to install Flash ClockworkMod Recovery on M701 (Apad)?

Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.

Custom Recovery Image
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.

Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.

Adb push issues
Clookeno said:
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.
Click to expand...
Click to collapse
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?

read only file
adb shell mount -o remount,rw /dev/block/mtdblock3 /system

The /nand folder needs to be read-writeable....since you use z4root go into temporary root and the push the file into /nand folder

Locobox said:
Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.
Click to expand...
Click to collapse
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....

poole699 said:
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?
Click to expand...
Click to collapse
poole699,
I have tried everything you can think of to put CM6 on the 2.2 Haipad firmware (which is really a modded 2.1) and had no luck. Either the system directories are all messed up or they locked the ability to edit it somehow. If you figure it out let me know because i have wanted to try it for a while.
I have a working team telechips 2.2 with market and correct orientation settings but it took ALOT of trial and error. If you go that route make sure you back-up your pointercal file because if you do not you will likely have to go back to an official release, save it, and try the telechips mod again...
Good luck

Clookeno said:
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....
Click to expand...
Click to collapse
Thanks again for the info, but I'm not familiar with ADB. The procedure seems difficult for me hope this thread helps a lot of other users!
Again thanks for the response.

M701 Screen Flip
Hi guys, I've got a bit of a problem with my M701 tablet. I did a factory reset the other day and now the digitizer is inverted. The screen works fine but when I touch the top it senses the bottom & left = right.
This is a complete pain in the arse.
I plugged the unit into a keyboard via the usb port as a workaround until I could get into it to try to resolve the issue but I'm now stuck in a loop at the sign in to google bit. Every time I sign in it takes me back to the sign in page.
This is also a complete pain in the arse.
It doesn't have clockworkmod installed and so when I tried to install update.zip as per the above post, it comes up with 'E:Failed to verify whole-file signature' error message and aborts.
Again, a complete... you get the picture...
So, I'm slightly frustrated with it to say the least and was wondering if any of you intelligent types could either point me in a suitable direction that doesn't involve the bin. Or a window...
Many thanks in advance.

Help
Locobox said:
Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.
Click to expand...
Click to collapse
How were you able to root your apad with Z4? I was not able to find the setting to activate the USB Debugging?
Thanks,
~b

is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?

ljohnso16 said:
is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?
Click to expand...
Click to collapse
I'm not sure if this of help to you, but I have a M701 2Gb (probable fake version), I've messed around with the basics on my exploring Android type thread:
http://forum.xda-developers.com/showthread.php?t=1004824
I've put recovery on both 2.1 and 2.3 roms (need different versions). Any other q's then let me know, I don't know much yet but learning the best i can.
A very useful place for info on the M701 is here:
http://www.androidtablets.net/forum/groups/11-haipad-m701-m701-r.html

[ROOT + CWM + OC KERNEL + Ubuntu] ZTE V11A / V71A / v55 HC3.2

The information provided in this thread is no longer up to date, although useful troubleshooting information can be found for those having issues. For those who would prefer to have the most up-to-date versions of CM9, CM10 or ParanoidAndroid supported by an awesome developer, go here
WARNING: IF YOU UPDATE YOUR TABLETS TO THE LATEST v03 UPDATES OF THE OFFICIAL ROM, YOU WILL LOSE THE ABILITY TO ROOT IT USING THE SUPERBOOT METHOD AND IT WILL BECOME A HUGE PAIN TO RE-INSTALL CWM/CUSTOM ROMS. INSTRUCTIONS FOR THIS SITUATION ARE PRESENTED BELOW, BUT PLEASE KEEP THIS IN MIND AND TRY TO READ THE THREAD CAREFULLY BEFORE MAKING SUCH CHANGES.
For those who need it, you can find a nandroid backup of Vodafone Romania's stock ROM for the v71a, here
Hello friends. With great thanks to utkanos, Koush and mobilx we now have a public alpha CWM and root available on both the ZTE V11A and the V71A, also known as the SFR StarTab 7/10, Vodafone SmartTab 7/10, as well as Sprint's (ZTE) V55 with credits due to utkanos for porting CWM, mobilx for being arguably the most motivated searcher of the holy root grail, and PaulOBrien from modaco and his superboot solution. We also thank alterbridge86 and eldarerathis for their advice and support. Additionally, credits go to joe.stone for custom kernel with loop device support, OC, touched voltages and a few other goodies.
Also, for interested developers, I have made the source code of the kernel available in a more easily accessible fashion. The source code (3 parts, contains the source for both models) is available here:
Part 1, Part 2, Part 3.
INSTALLING CWM:
A new optimized version of CWM for 7"and 10" tabs has been put together by joe.stone. I will also keep utkanos' links available below for those who prefer his versions or wish to thank him for his early efforts in making our tablets awesome
joe.stone said:
For those who have troubles with cwm recovery (freeze while backup ) i have created a new version. Flashable from fastboot.
10" CWM Recovery
7" CWM Recovery
Credit goes to joe.stone.
Click to expand...
Click to collapse
joe.stone said:
If you updated your tablet ROM via OTA or updater exe and can no longer install CWM, follow the following instructions:.
In firmware v03b fastboot flash is disabled and from a running system flash_image will fail too.
Download the twrp recovery http://goo.im/devs/joestone/twrp/v71_recovery.img
download the twrp recovery zip flashable version too
http://goo.im/devs/joestone/twrp/V71A_TWRP.zip
download kernel #60
http://www.4shared.com/zip/tzrUo5_N/v7_kernel_60.html?
copy the two zip files to the sdcard
If you want flash kernel#60 then do the following:
adb reboot bootloader
the tablet will reboot and you will get only a blank screen . Be sure that the drivers are installed from windows update for the fastboot interface.
check it with : fastboot devices. If you get waiting for device the drivers are not installed.
fastboot boot v71_recovery.img
The twrp recovery comes up. Now you can install twrp by selecting install menu. Browse to the v71twrp.zip on the sd and install it. Now you have permanent twrp recovery.
now go back to install menu browse to the v7_kernel_60.zip and install it.
reboot and enjoy.
These are kernel #60 links for the other models :
Sprint Optik (V55)
http://www.4shared.com/zip/RTZrSXyV/v55_kernel_60.html?
SmartTab10 (V11A)
http://www.4shared.com/zip/PrW1TWHF/v10_kernel_60.html?
OR
You can flash cwm using adb , you need root rights .The best is when adbd is running in root mode (for eaxample kernel#60).
Download this :flash_image binary
then turn on usb debugging.
to flash cwm you need the following commands:
adb push CWMrecovery.img /data/local/tmp
(where cwmrecovery.img is the name of the cwm image file name.)
adb push flash_image /data/local/tmp
adb shell chmod 755 /data/local/tmp/flash_image
adb shell (you need # not $ for flashing , so if you got $ type su to get #)
cd /data/local/tmp
./flash_image /dev/block/mmcblk0p18 CWMrecovery.img
Dont forget to remove the install-recovery.sh file from /system/etc othervise it will install stock recovery at system start if it has not the stock recovery.
To revert the bootloader you need to flash NON-HLOS.bin"to "/dev/block/mmcblk0p1" and "emmc_appsboot.mbn" to "/dev/block/mmcblk0p7" from a previous version .
Click to expand...
Click to collapse
Utkanos' v11a version is here.
Utkanos' v71a version is here.
Credit goes to utkanos, mobilx and koush. I have also attached these files at the end of the post.
Also attached, is the original 7-inch stock recovery file, for users who may wish to return to stock and have not performed backup.
--> Plug your tablet into usb, launch a command line, and use "adb reboot bootloader"
--> Download the CWM Recovery image from the link that fits your device.
--> Place it into the adb/fastboot folder (I am assuming you have downloaded fastboot already from the link above, during the root procedure).
--> In the command line, navigate to that folder (use "cd <path>").
--> input the command "fastboot flash recovery <filename>".
--> Reboot into recovery mode (should be Power + Volume down).
--> You should now be in CWM Recovery, and can now attempt to perform a nandroid backup.
Also, in order to prevent a possible hang, you should:
--> Reboot the tablet into the Android OS;
--> Mount it through USB;
--> Go into the clockworkmod folder;
--> Create an empty file with no extension called ".hidenandroidprogress"
After a period of testing this will be submitted to the Koush's Rom Manager. Source code is also available herehere, linked from utkanos' post.
What works:
Nandroid backup/restore on internal sdcard
Battery stats wipe
Dalvik wipe
Cache wipe
etc.
What does not work so far:
USB mass storage
credits:
utkanos
Koush
Click to expand...
Click to collapse
Modified Kernel Available, all credits to joe.stone, give him thanks here:
joe.stone said:
Here it is.
There is a new kernel version available. The new version is #60 and flashable from cwm recovery .
Changelog :
-Revert GPU overclock
-Revert change of system audio files (because of bootloops on some devices after installation #55)
-Increased system volume on kernel level
-Changed VMALLOC_RESERVE=0x19000000 to VMALLOC_RESERVE=0x10000000
-Added Apple Magicmouse HID support
-Added Microsoft HID support
-Changed cpu minimum freq 345MHz to 432 MHz to avoid the black screen effect (the screen does not wake up , you have to reset )
V55_kernel_60.zip Hope will work fine on v55.
V7_kernel_60.zip
V10_kernel_60.zip
Click to expand...
Click to collapse
Also, Benny3 has put together a CWM-flashable ROM package for the V55 tablet, including Joe's kernel #60 and a number of useful goodies. You can thank him and download the package from here.
Both device (v71, v11) were migrated into one kernel tree , so they both use the same source. (In case of v71 it is much newer source)
The whole kernel source was updated from the v55 sources .
Now they are in cwm recovery flashable format , because this package updates the kernel modules too in /system/lib/modules and enables to use the agps and NTP server setting was corrected . It points to europe.pool.ntp.org instead of the test one . Now my tab finds position within seconds . With the new kernel for me it seems the touchscreen is much better , but as before I am waiting for the feedbacks. Other fixes include: Touchscreen sensitivity, USB Charging etc.
Installation :
download the zip file
copy it to your tab's internal storage
start the tab in clockworkmod recovery
select install zip from sdcard
select the file for your model
install
reboot
and stock kernel for 10" :
stock kernel[/QUOTE]
Finally, if you want to obtain a dump of boot.img, please consider the following advice, also by mobilx, here:
mobilx said:
It is a mmcblk device not mtdblock
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
Click to expand...
Click to collapse
ROOTING:
mobilx said:
It is recommended that you skip these steps and proceed to flashing clockwork mod for your respective device from the start using fastboot, and from inside CWM install joe's kernel (or custom rom), which you can find below. Joe's kernels and rom already come with significant updates to stock Vodafone systems, and are pre-rooted.
We will use superboot to root. What does superboot do? It puts the SU binary and makes a 'insecure' kernel to be loaded temporarily on to the device through ADB remount. So it's only purpose is to make ROOT. After execution, you will still be on the stock kernel, only with root privileges.
This method is for the advanced users only who want to have root before we have a fully functional CWM running. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What will you need?
--> Download Fastboot+Superboot.img from here.
--> Install ADB through the SDK, download from here, although the ADB included with the ZTE drivers should also work.
--> Install the ZTE drivers, you can find them here, although they should already be included on your device when first mounting it.
--> don't forget to enable USB debugging in the tablet's application settings.
--> Put the fastboot.exe and the superboot.img files in the working directory you will be running adb from (Default should be at "C:\Program Files\ZTE Handset USB Driver".
--> Open a Command Line (Start Menu > Run > CMD) and navigate to the working directory. (Use "cd C:\Program Files\ZTE Handset USB Driver" or alter the path accordingly).
--> Write the following commands withing the command line:
--> adb reboot bootloader
--> fastboot boot superboot.img
--> The device should now boot with the Superuser.apk installed and SU in the /system/xbin/su, as well as allowing you adb root commands. Now run the following:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
--> You can now exit the ADB shell and reboot the tablet.
--> Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution
Click to expand...
Click to collapse

Reserved for future posts

I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.

assdksl said:
I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
Click to expand...
Click to collapse
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.
Click to expand...
Click to collapse
Haven't looked for it, but so far accessories for this line of devices seem to be lacking. With the popularization by Vodafone and the launch of the new Sprint V55 and similar tablets, these accessories should become more popular.
I haven't had any problems with the time on my device, sounds really weird.

assdksl said:
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Click to expand...
Click to collapse
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.

Thank you both for quick answering my questions.
mobilx said:
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.
Click to expand...
Click to collapse
Yes, indeed, but when I untick sync with Network-provided time, clock is ticking faster then it should.
It seems that clock chip on my device is not calibrated well or there is some other bug, it seems that it is HW issues... this is little more explained here:
http://blogs.keynote.com/mobility/2...wrist-watch-android-doesnt-keep-the-time.html
It seems that I was unfortunate and get device with bad clock, also without root I'm unable to use ClockSync app that will solve my problem.
But what is bugging me, is the fact that I also have SGS I9000, and it is synchronizing with Vip network just fine.
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
Click to expand...
Click to collapse
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.

assdksl said:
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
Click to expand...
Click to collapse
Yes it happend to me once. First I unticked the network-provided time sync and after restart I ticked it again. The clock is fine since than.

assdksl said:
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.
Click to expand...
Click to collapse
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
These are some of the useful bits of advice I received that could probably be put to good use when I have some free time. If you feel that anything is helpful, feel free to try it out.

sangemaru said:
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
Click to expand...
Click to collapse
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Click to expand...
Click to collapse
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

assdksl said:
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
That's fine. We have a dev utkanos who agreed to build the CWM for our device. He is very experienced in this stuff. The only way to build a proper CWM is to get a boot.img dumped or extracted from a leaked ROM.
So what we need to do:
Get root via some exploit (there is none for 3.2 HC yet) , dump boot.img and build CWM, flash CWM with fastboot, or
Find leaked ROM , extract boot.img, build CWM, flash CWM with the fastboot, root device with Update.zip
Yes the fastoboot is working and the bootloader is unlocked.
I have tried these exploits so far:
GingerBreak
psneuter
zergRush
Also I have tried:
Acer iconia 100 method ADB
Acer iconia 500 method
All ideas are welcome.

Ladies and gentleman the ROOT is here Device is successfully rooted with the superboot method.
Thanks to my friend sangemaru who made this possible.
Expect CWM soon. utkanos is working on it.
Need some testing, before this goes to public

That's great news mobilx! Looking forward to a root and ICS sometime in the future

Congrat`s guys,nice work and many thanks from all users.
This is a beginning of a beautiful friendship with SmartTab
We expect nice custom roms and maybe in a short time and ICS rom for this excellent tablet.
If I or we (other members) can help with something,please,let us know,i dont know programming but i can use Paint (just kidding)

Jeeej!!! I'm looking forward to it!

Ok lets roll
While we are waiting for CWM to be build we can root ZTE V11A/V71A aka Vodafone SmartTab 10/7 with the superboot.
What the superboot does? It puts SU binary and makes a 'insecure' kernel to be loaded temporally on to device( ADB remount). So it's only purpose is to make ROOT. After reboot you are on your old kernel but with the root.
This method is for the advanced users only who want to have root before we build a CWM. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What we need?
ADB installed through SDK
Zte drivers installed --> debugging ticked in options
fastboot + superboot.img --> Put files in the adb working dir
>adb reboot bootloader
>fastboot boot superboot.img
Device should boot with Superuser.apk installed and SU in the /system/xbin/su.
>adb remount
>adb shell
#ln -s /system/xbin/su /system/bin/su
Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
#exit
$exit
>adb reboot
Device will reboot with the stock kernel but rooted.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution

Thx mobilx! Hvala

All it's OK
It's working also on v71a.......LOL
10x man

urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
I can also confirm this working on 7 inch

urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
jakaka said:
I can also confirm this working on 7 inch
Click to expand...
Click to collapse
That is great guys. sangemaru will be very happy because he owns A71A
So you can confirm that it boots and the touchscreen is working? That means the kernel is the same for those two variants.

V17A
YES, all work perfectly...........setcpu, blackmarkt,root uninstaller, lucky patcher, etc
The only differences between v11a and v71a is the size of the display
we are wating for CWM..........10x again
v71a

Full root for A700 and A701 tablets

WARNING. THIS is ONLY for tablets running ICS. If you are running Jelly Bean, You May Brick your device!!
Again, this is for ICS ONLY!
Running this root on a Jelly Bean OS can cause your tablet to stop functioning as it is designed for ICS only. If you have a Jelly Bean Operating system, then please use Vorbeth's or Moscow Desire's Easy Root Package located in the Development Forum. If you do not know which OS you currently have, then you should ask questions before rooting.
Method 1. Universal for A700 and A701 Tablet
1. Enable adb mode: Settings -> Developer options -> USB debugging - check it point.
2. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
3. Download arhive. Unpack it to any place.
4. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
runit.bat
Your firmware is now rooted.
5. At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
------------------------------------------------------------------------------------------------------
Method 2. With the patched kernel from the A700 tablet
For ICS A700 firmware only!
1. Enable adb mode: Settings -> Developer options -> USB debugging - check it point.
2. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
3. Download this arhive. Unpack it to any place.
4. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
flash-ICS-patchedBoot.bat
Your boot.img is now patched and firmware is now rooted.
5. At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
6. Now you will have to install the following programs:
BusyBox
Titanium Backup
7. Run BusyBox and go through the install steps. During this SU should ask permission to give BB root access, if it does, it worked!
------------------------------------------------------------------------------------------------------
Method 3. From CWM recovery for A700 and A701 Tablet - Not available due to problems in the work of CWM recovery!
1. At the tablet must be installed CWM recovery.
2. Download arhive ICS_Rooting_recovery.zip. Put it on SD-card. Insert the SD-card in the tablet.
3. Run CWM recovery on the tablet and flash ICS_Rooting_recovery.zip.
Your firmware is now rooted.
4. Now you will have to install the following programs:
SuperUser
Titanium Backup
At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
------------------------------------------------------------------------------------------------------
Method 1, in contrast to method 2, does not affect the core of the system. This makes it possible to receive future firmware update. But only if you do not forget to make backups before making changes to the system and restore it before upgrading.
PS: I tried to make a method 1 as safe as possible. But I have not had a chance to test it completely. So if it does not work, be sure to let me know in this thread and I modified it.

great work ! Thank you for this :good:
BTW the the script is called "flashpboot.bat" and not "flash-ICS-patchedBoot.bat" in the archive.

Really great thanks for it.
Just a question, can it be unrooted/undone by flashing 028-stock rom?
Gesendet von meinem A700 mit Tapatalk 2

KruSan said:
Really great thanks for it.
Just a question, can it be unrooted/undone by flashing 028-stock rom?
Gesendet von meinem A700 mit Tapatalk 2
Click to expand...
Click to collapse
yes

the patch with Acer_AV043_A700_1.028.00_EMEA_FR doesn’t work after flashing the patched boot the tablet doesn’t boot it stuck at Acer logo

moom999 said:
the patch with Acer_AV043_A700_1.028.00_EMEA_FR doesn’t work after flashing the patched boot the tablet doesn’t boot it stuck at Acer logo
Click to expand...
Click to collapse
same problem here

moom999 said:
the patch with Acer_AV043_A700_1.028.00_EMEA_FR doesn’t work after flashing the patched boot the tablet doesn’t boot it stuck at Acer logo
Click to expand...
Click to collapse
Rename Acer_AV043_A700_1.028.00_EMEA_FR to update.zip and put it in an external sd card.
There's a startup mode that installs it automatically, you have to press the left volume+power buttons at startup if I remember well.

alx5962 said:
Rename Acer_AV043_A700_1.028.00_EMEA_FR to update.zip and put it in an external sd card.
There's a startup mode that installs it automatically, you have to press the left volume+power buttons at startup if I remember well.
Click to expand...
Click to collapse
you missunderstand, they mean, when you have 1.028 you cant flash the patched bootloader because they stuck onn boot screen

No problem to flash again Acer_AV043_A700_1.028.00_EMEA_FR or Acer_AV043_A700_1.025.00_EMEA_CUS1
The problem the patch doesn’t work with any of this two rom

moom999 said:
No problem to flash again Acer_AV043_A700_1.028.00_EMEA_FR or Acer_AV043_A700_1.025.00_EMEA_CUS1
The problem the patch doesn’t work with any of this two rom
Click to expand...
Click to collapse
The size of the patched bootloader seems wrong, I guess that's why it's faulty.

OK, so how do we fix this ??
Edit, reflashed with update.zip, so all OK, phew !

Cannot reproduce with Acer_AV043_A700_1.028.00_EMEA_FR !
Just stays at Acer logo with unlocked bootloader and forces me to re-install as update.zip which leaves me without root.

Which Firmware is working ?
Has anybody allready tested with which firmware this method is working and with which not ??

Be careful, same issue on NORMAL french firmware, not the crappy totally unknown one everybody seems to like, so i guess that's it : this patch STUCK YOUR TABLET ON ANY KNOWN FIRMWARE THIS FAR

Okay, so i just tried to push insert the superuser.apk into the Acer_AV043_A700_1.028.00_EMEA_FR file and flashing this, but as i was expecting, it didn't work out... it didn't even install.
edit: i can confirm, that it does neither work with the Acer_AV043_A700_1.028.00_EMEA_FR, nor the Acer_AV043_A700_1.025.00_EMEA_CUS1 !
so, i guess we have to wait for ZeroNull to come up with another way to get this to work.

Flashboot.bat not responding
I unlock my bootloader with Blackthund3r's A510 Bootloader Unlocker v1.0.0 and go the "unlocked" status. Rebooted the tablet, went into the patched-boot folder and ran as administrator "flashboot.bat". The screen displayed a bunch of what looks like gibberish and when I pressed the Enter key, the screen went to :
"Flashing patched boot.img
<waiting for device>
Then the process just sits there and doesn't go any further. Am I missing something in what I am doing?
---------- Post added at 02:27 PM ---------- Previous post was at 02:18 PM ----------
I used Root Checker Pro to verify root and here is what the app displayed:
"Root Access is not properly configured or was not granted.
Superuser Application Status:
Superuser application - version 3.0.7 installed!
(I had downloaded and installed this from the Market after the first attempt failed)
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1"
Anybody got any ideas on what to do next?
Thanks!

You have to reboot into bootloader for the script to work.
But if you had read the comments above, you might have seen, that the described method does not yet work and several people state, that after flashing the Boot.img the device is stuck in boot.
Gesendet von meinem A700 mit Tapatalk 2

Just to be clear : This method specific to A700 does not work at all yet BUT this WORKS PERFECTLY with the A701 patched rom ZeroNull released at the same time
check this post for the a701 patched rom, you don't need to put it on sdcard it includes BAT files to flash it all from bootlader
http://forum.xda-developers.com/showpost.php?p=27742776&postcount=39

Hello jpearn or doanb555,
With which release of the "update.zip" you can restore your Iconia Tab A700 ?
thx

spoque said:
Hello jpearn or doanb555,
With which release of the "update.zip" you can restore your Iconia Tab A700 ?
thx
Click to expand...
Click to collapse
i'm not jpearn or doanb555 but what kind of question is that ? you got only two roms, both are working. what's your point ?

How can I extract the stock firmware from my Phone without TWRP or root?

I have a new Moto G Stylus 5G 2022 (XT2215-4) that I would like to compile lineage for. However TWRP does not currently support my device and therefore I cannot find any recovery images for my phone. Since I can't use TWRP yet I also can't root my phone yet.
I am willing to attempt to compile TWRP for phone from source but I will need .img's from the stock firmware to do that.
How can I extract the stock firmware off of my phone so that I can create the recovery files for my device?

Without root you can't.

xXx yYy said:
Without root you can't.
Click to expand...
Click to collapse
So if you can't root without recovery, and you can't get recovery without having root, how does anyone ever do anything with their phone?
Quite the catch 22.
I have only found a handful of sites that claim to have the stock firmware available for download. however all of them are essentially skins of each other and in different languages. Not legit at all.
Does Motorola release their own stock firmware?

1. Android Recovery is a minimalistic Android OS what allows you to perform some basic operations, has nothing to do with Root what is an Android OS function.
2. Root since Android version 6 is part of every full fledged Android OS - keyword: Toybox.
If OEM has eliminated su binary from Toybox then you have to add su binary to Android OS at your own.

xXx yYy said:
1. Android Recovery is a minimalistic Android OS what allows you to perform some basic operations, has nothing to do with Root what is an Android OS function.
2. Root since Android version 6 is part of every full fledged Android OS - keyword: Toybox.
If OEM has eliminated su binary from Toybox then you have to add su binary to Android OS at your own.
Click to expand...
Click to collapse
I get #1 and semi understand what you are saying in #2.
Alternatively, I have been able to acquire the stock firmware for my phone from Motorola using their own rescue and assistance tool.
Now I am working on extracting the system image from the super sparse chunk files provided in the firmware.

Tokth said:
I get #1 and semi understand what you are saying in #2.
Alternatively, I have been able to acquire the stock firmware for my phone from Motorola using their own rescue and assistance tool.
Now I am working on extracting the system image from the super sparse chunk files provided in the firmware.
Click to expand...
Click to collapse
Erm actually your firmware should be on the Lenovo Recovery Tool. This is how we got the boot.img for the Moto G Stylus 5G (2021). When you select it to recover your device it downloads the devices firmware. All you have to do is extract the boot.img from the applications download folder and then patch it with magisk and flash it if you have an unlocked bootloader already. Then you can extract whatever vendor blobs you need to create a working TWRP for your device.
Would you let me know if this works?

Tokth said:
So if you can't root without recovery, and you can't get recovery without having root, how does anyone ever do anything with their phone?
Quite the catch 22.
I have only found a handful of sites that claim to have the stock firmware available for download. however all of them are essentially skins of each other and in different languages. Not legit at all.
Does Motorola release their own stock firmware?
Click to expand...
Click to collapse
Without root or TWRP, they don't/can't do anything that requires accessing/modifying anything other than user data. Extracting the "ROM" requires root or TWRP because it resides in the system partition which can't be accessed by the user without root or TWRP.
No, it isn't a "catch 22", it is the way android is designed bacause the manufacturers/carriers never intended for the user to have access to system in the first place.

Droidriven said:
Without root or TWRP, they don't/can't do anything that requires accessing/modifying anything other user data. Extracting the "ROM" requires root or TWRP because it resides in the system partition which can't be accessed by the user without root or TWRP.
No, it isn't a "catch 22", it is the way android is designed bacause the manufacturers/carriers never intended for the user to have access to system in the first place.
Click to expand...
Click to collapse
You are correct.

tnuoccaadx2 said:
If I am rooted, how do I extract the firmware without twrp?
Click to expand...
Click to collapse
With adbshell(not adb) or a terminal emulator using dd commands, you just need to make sure you correct command and location of each partition that you want to pull a copy of.
Do a Google search for:
"How to extract copy of stock recovery via adbshell"
Or
"How to extract copy of stock recovery via Terminal Emulator"

tnuoccaadx2 said:
As for the stock firmware is there a guide for the dd cmds so i may see an example and a guide on how to find partition location?
Click to expand...
Click to collapse
That was the point of doing the searches I suggested. It should get you going in the right direction learning how to use dd command and how to identify your partitions.
Also, you could just download your stock firmware and extract what you need from the firmware file.

You don't always have to make use of
Code:
adb shell "<SHELL-COMMAND-HERE>"
Running
Code:
adb exec-out "<SHELL-COMMAND-HERE>"
does the job as well. The best solution is to use adb exec-out command !
Example:
Code:
adb exec-out "dd if=/dev/block/by-name/whatever of=/sdcard/whatever"
FYI:
exec-in and exec-out are present since Android 5.
exec-in and exec-out can write/read to/from only files, not STDOUT/STDIN.
Important:
If it does not work - it means that your phone does not support the command properly.