Related
hi all
just wanted to star a discussion about this topic..
anybody know, how's the progress in getting a CWM for MediaPad?
thanks a lot
Backup works, but restoring a backup doesn't restore every setting. So i would say it's a WIP. But maybe segler11 or brainmaster can tell more about it.
Eagerly awaiting for this to be done.
Androod-hilfe.de has a clockwork RECOVERY.
Gesendet von meinem HUAWEI MediaPad mit Tapatalk
Is there a way to get a hold of this?
Sent from my HUAWEI MediaPad using XDA
I would love to break my tablet in the name of getting it to work
Sent from my HUAWEI MediaPad using XDA
@cosmique
Like I said, it's a WIP and restoring a Backup doesn't work 100% afaik... But if someone wants to try it here, go ahead. I'll upload it.
€dit: Done
Original Thread: here.
WARNING: I'm not responsible for any damage on your devices. This has only been tested on a european Huawei Mediapad and is based on the 2nd Preview of ICS
Code:
fastboot flash recovery recoveryxxxx.img
fastboot flash recovery2 recoveryxxxx.img
Important: If you want to restore a backup use
Code:
wipe data/factory reset
wipe cache partition
first !
After a "wipe data/factory reset" and "wipe cache partition" the first boot could take at least 10 minutes.
If you want to flash AddOns like GApps.zip no wipe is needed
After restoring a Backup, ALL apps are restored but not all app-settings.
Remember: It's a BETA-Release !
Click to expand...
Click to collapse
All credits go to DS7005, segler11 and brainmaster
Just a helpful hint: Titanium Backup can now restore app data directly from nandroid backups. So if the biggest issue right now is failure to restore app data, in a pinch Titanium can fill in the blanks.
Sent from my Galaxy Nexus using Tapatalk
Recovery flashed successfully but when I perform a backup, it says that the backup path can't be mounted. This is on a Springboard running ICS Beta 2.
Bump. Any further progress?
So it has been quite some time since I have heard anything about CWM for our device. Does anybody have an update? What the heck ever happened with the folks working on it over in Germany?
rkwhyte2 said:
So it has been quite some time since I have heard anything about CWM for our device. Does anybody have an update? What the heck ever happened with the folks working on it over in Germany?
Click to expand...
Click to collapse
Last time I tried the download at post #7 it worked for the basic. As described by Rumbi it may not restore widgets and some setting.
The downside is that you have to reinstall original "boot.img" and "recovery.img" to be able to update to next version, every time
I think that as things get stabilized on the ICS firmware there will be more work for it !
Question: Is there any recovery.img available that would be equivalent to stock recovery on a Springboard?
In other words... if I upgrade a Springboard to MediaPad ICS... then later revert to 3.2 from a nandroid backup, is there a recovery.img that I can flash so that OTA updates will work again?
Okay I flashed the CWM img successfully in fastboot on my Springboard...
But what I'm confused about is, how do I boot into recovery now? I have tried every combination and I always get either fastboot or regular boot.
Do I have to already have ICS for this recovery to work?
Update: Ok I managed to figure out the trick is to hold the volume down button, press power for 2 seconds until it vibrates, let go of power and continue holding the volume until recovery starts.
The problem is I always get stock recovery, which gives me a FAIL message.
I discovered that on my Springboard I have the May 2012 OTA update already installed, which included the dreaded /system/recovery-from-boot and /etc/install-recovery files. This means any time it boots successfully into the OS, it reinstalls the stock recovery.
So now I have a paradox because I'm still not rooted yet. I can install CWM from fastboot, but there is no way to cleanly power down the tablet. I have been unable to force it from fastboot directly to recovery, because the only way to get it out of there is to hold down the power button which... yup, starts rebooting into the OS. I can hold down power during that reboot cycle, but again it just initiates a reboot and not a power down.
So how do I get into recovery after flashing CWM in fastboot... without letting it boot the OS before I get there?
So far the only idea I have remaining is to flash CWM in fastboot and then just leave it on the fastboot screen, stick it in a box somewhere, and come back in a day or so when the battery has died. Charge it up and then boot it into recovery. A little extreme?
Boot into fastboot normally pressing power and VOL-
When in fastboot press the power button for 10 sec to reboot and then keep pressing the VOL+ button, it'll show the mediapad logo twice and the you will be in the cwm.
Hope it helps.
dark_fighter said:
Boot into fastboot normally pressing power and VOL-
When in fastboot press the power button for 10 sec to reboot and then keep pressing the VOL+ button, it'll show the mediapad logo twice and the you will be in the cwm.
Hope it helps.
Click to expand...
Click to collapse
I tried that. It just booted into the OS.
Also the Springboard firmware has an annoying loud T-Mobile startup chime, so to be considerate with my roommate, the moment I see it booting into the OS I have to wrap it with my duvet in order to muffle the sound
Is it possible this CWM just isn't compatible with the Springboard on Honeycomb?
Just a question... if you want to update to ICS but stock, why don't you use the official rom from Huawei? and If you don't like it you can always flash back a HC rom from Huawei.
Sorry if I didn't get something and this is a stupid suggestion
Huawei doesn't offer any stock ROM files for the Springboard. I would like to install and run CWM from the Springboard while leaving the T-Mobile Honeycomb intact, in order to root it without any other modifications.
Sent from my Galaxy Nexus using Tapatalk 2
UPDATE: I did not notice at first that I had to flash both recovery *and* recovery2.
Even after noticing this, I was unable to leap from fastboot straight into recovery. However, I left it in fastboot this morning after flashing, to drain the battery. Then I got home and plugged it in to charge for about 5 minutes. I unplugged it, used the recovery key combo, and FINALLY made it into CWM! I used an SD adapter to copy su.zip onto the microSD, plugged in, remounted /sdcard and installed that zip. I have plugged it back in to charge, and I am doing a nandroid backup of stock rooted.
First thing I will have to do once booted is install Root Explorer and rename the offending files that keep replacing CWM. Then I'll be off to the races.
EDIT: The backup stalled during the system partition. Don't know why. Maybe something different about the layout of Springboard vs. MediaPad.
Also, adb in recovery does not work (unless there is a driver I am missing? but ADB works for me booted into the OS). That's unfortunate - this is an incredibly useful feature of CWM that should get fixed up ASAP.
I also noticed that a 10 second press of the power button actually shuts it down from CWM, as opposed to the reboot I get from fastboot or anywhere else in the OS.
EDIT again: Oh crap crap crap. Now it just bootloops when I try to start it up! This does not bode well. All I did was install a superuser zip, and attempt a nandroid backup.
FINAL edit once more again: Okay well now I'm back to square minus one. I wiped userdata and it still bootlooped. So then I tried flashing the system img from this thread:
http://forum.xda-developers.com/showthread.php?t=1550694
No more bootloop. It's booted up. The firmware is now an older one than what I received it with. Oddly when I did "fastboot erase userdata" from fastboot it did NOT actually wipe anything! It still remembers my desktop, wifi passwords, installed apps etc.
On the bright side - the dreaded recovery-reinstalling files are not in this system.img.
Hi, my G3 (vs985) was running 24b, rooted, and I installed TWRP Manager and installed a custom recovery. all went fine until I got a secure boot error whenever I booted to recovery. After tinkering and thinking I found a possible solution, I used autorec which gave a Success in installing twrp, and booted back in to recovery where I got a into an LG Security Error and would continue switching between the logo and the security error screen. I was still able to get into twrp through the factory recovery menu and going to factory reset which sends me to twrp. I tried restoring a backup I had previously made, and that went successfully but now my issue is that I'm stuck in a boot certification error with the light blinking blue and red and I am unable to get into download mode, but am still able to get into twrp and get into my phone's files. I don't trust myself anymore, and would absolutely love some guidance on this. If I do try to go to download mode, and I connect it to my pc, my pc makes the noise as if it were connecting, and the phone vibrates, but the screen turns black and nothing "seems" to pop up. I can try to answer any questions, I am somewhat new to this. Thank you in advance!
EDIT: The error I'm currently getting is:
"Secure Boot Error
Cause: Boot Certification Verify".
I'm guessing that you used the 23C autorec which put the wrong bootloader on the phone for 24B. From TWRP. I'd create a backup in TWRP, dirty flash JasmineROM 8.0 (in other words, no wiping), then you should be good.
I had this yesterday. Did the same thing.
I finally resolved it by getting back into TWRP from the OEM recovery, Full System Wipe menu item. TWRP allowed me to mount the storage on my computer and flash SkyDragon 5.0. I still can't get back into recovery, but at least the phone works better than stock Lollipop.
BoulderGeek said:
I had this yesterday. Did the same thing.
I finally resolved it by getting back into TWRP from the OEM recovery, Full System Wipe menu item. TWRP allowed me to mount the storage on my computer and flash SkyDragon 5.0. I still can't get back into recovery, but at least the phone works better than stock Lollipop.
Click to expand...
Click to collapse
Boulder, I'm not sure I understand what you wrote, twrp is recovery, so if you can flash using twrp are you just unable to access it ...it must me installed on your phone? I haven't flashed using the computer in a long time, so it's not really fresh in my mind what you did. If you power down your phone, then hold the power and vol down button simultaneously, it will reboot, release buttons, then as soon as you see the lg logo, press the power/volu down simult. again, and it will take you to a screen that gives you options you can choose using the volume up/down keys to navigate and power to choose a button. Wipe cache would take you into twrp if it is indeed installed on your phone. If you can access twrp however you did previously,you can flash a zip file of twrp (I use 2.8.7.0, I think it is the newest, it is newer than what was in autorec that I tried last night). Wipe davalcik/cache after you flash the twrp zip and reboot your phone and you should be fine....although I think you may actually have twrp already (hence 'recovery"} based on what you posted. Good luck.
I did flash the 23C version of Autorec into my 24b phone. This gave me the Security Error bootloop.
Eventually I was able to get into LG stock recovery with the volume down button. Magically, hitting Factory Wipe brings me to the hidden TWRP. From there I flashed base SD5.0. In Android, I installed the Autorec 24b apk and reinstalled TWRP. This again security looped.
Now, I can't even access LG bootloader or TWRP. Even the QuickBoot app fails to boot to revovery. But, the phone works, so I don't want to break it further. Might just wait for a development upgrade to SkyDragon.
After seeing a few people arguing over whether or not it is possible to downgrade from Lollipop to KitKat while maintaining root, I decided to give it a try....and it worked!!
Below are the exact steps that I took in order to downgrade. Please attempt at your own risk!
1. Backup contacts and all user apps onto an external location (SD Card, computer, etc).
2. Download the NK1 firmware and place it somewhere on your phone's internal storage. I got my firmware from SamMobile.
3. Download and install FlashFire.
4. Backup your device using FlashFire in case anything goes wrong. Make sure to save the backup on your external SD Card!
5. After completing the backup, your device should reboot. Proceed to open FlashFire again, this time selecting the "Firmware" option from the pop-up menu.
6. Select the NK1 firmware and allow it to verify. Then press "Flash" at the bottom of the screen.
**** 7. After the firmware flashed successfully, my phone got stuck on the red Verizon boot screen. After letting it sit for 5-10 minutes, I pulled the battery. I then reinserted the battery and booted into recovery mode (hold power, volume up, and the home button during boot) and did a factory reset. ****
8. After the factory reset, I rebooted once more and the phone started successfully.
9. The SuperSU application is located within the app drawer, however, it never fully loads upon opening....BUT, I do have root access and all root applications I have downloaded have been successfully granted superuser permission.
So there you have it! Not the safest procedure, but it certainly worked for me! If you end up downgrading and losing root, you should be able to upgrade back to 5.0, root, and try again.
**EDIT** - The reason this works is because when you flash a firmware package using FlashFire, regardless of which firmware it is, SuperSU is always injected during the flash. Not sure if it's just luck that it happens to work when downgrading to 4.4.4 or not... But that's what I have been able to gather.
Hello, I need a little advice on getting my phone working again. I got a new Ramos MOS1 Max today and rooted it via Kingo PC software. I checked to make sure it was rooted using RootChecker and it said it was rooted. I was reading up on what to do next and some sites said the next thing you must do is to make a backup of your phone via TWRP. I installed the software and then attempted to use the "reboot and create backup" functionality. The phone rebooted and I was in the Android system recovery menu. I didn't see anything like what TWRP was supposed to show, so I just rebooted via the standard recovery screen method. Now when I try to start the phone, it gives me a logo, then ARMPHONE and it hangs on that.
I've tried wiping my cache partition via recovery menu and rebooting, but no dice. Next they suggested to do a wipe data/factory reset, and since I just received the phone today, I decided to try that. After doing that via system recovery menu it still wouldn't boot past the ARMPHONE screen. I don't have a lot of experience with rooting and modifying Android devices, is there something I can do to fix this? I've installed the android SDK tools for my version of android (5.1 I believe), but I don't know how to proceed. Is there a stock image I can use for this phone, or can I just use a vanilla android image?
Thanks in advance.
sphericon said:
Hello, I need a little advice on getting my phone working again. I got a new Ramos MOS1 Max today and rooted it via Kingo PC software. I checked to make sure it was rooted using RootChecker and it said it was rooted. I was reading up on what to do next and some sites said the next thing you must do is to make a backup of your phone via TWRP. I installed the software and then attempted to use the "reboot and create backup" functionality. The phone rebooted and I was in the Android system recovery menu. I didn't see anything like what TWRP was supposed to show, so I just rebooted via the standard recovery screen method. Now when I try to start the phone, it gives me a logo, then ARMPHONE and it hangs on that.
I've tried wiping my cache partition via recovery menu and rebooting, but no dice. Next they suggested to do a wipe data/factory reset, and since I just received the phone today, I decided to try that. After doing that via system recovery menu it still wouldn't boot past the ARMPHONE screen. I don't have a lot of experience with rooting and modifying Android devices, is there something I can do to fix this? I've installed the android SDK tools for my version of android (5.1 I believe), but I don't know how to proceed. Is there a stock image I can use for this phone, or can I just use a vanilla android image?
Thanks in advance.
Click to expand...
Click to collapse
You can find the firmware here http://4pda.ru/forum/index.php?showtopic=783029
I'd say I'm above average when it comes to rooting and installing ROMS, but this one has be stumped. It may just be that I simply need to flash the stock ROM and try again, but here's my dilemma.
I successfully installed the correct version of TWRP for my tablet, as was I able to root it, but Xposed posed an issue. Upon flashing Wanam's custome Xposed zip, I am got the dreaded "Encryption Failed" screen. Assuming that Wanam's custom Xposed zip is what I need, because I'm using a Samsung device, what might I have done wrong? I have now formatted and wiped everything and am back to the setting up the device run through, but TWRP is still installed. If I do need to flash the stock ROM (firmware), I can't because I have not found it when searching here or Google.
If anyone has successfully installed TWRP, rooted, and installed Xposed on this tablet, I beg of your assistance. Also, a link to the stock firmware would be amazing.
EDIT: I will add that after I was able to get back to setting up the tablet and no longer facing the "Encryption" boot loop, as well as flashing Wanam's Xposed uninstall zip, I no longer have root and flashing the Chainfire SuperSU does not give root, but brings back the "Encryption" boot loop.
EDIT 2: I have found the stock firmware for this tablet. I found it on two file hosts. One is the well-known RapidGator. The other is an obscure (to me anyway) filehost called Alfafile. I am downloading it from Alfafile because RapidGator makes you pay for their premium service to download a file this large (1.6 GB), but the speed is awful to say the least. Once I download it, I want to share it. Where could I upload this that it would be available to everyone without paying a premium price, a site we are allowed to link on here??
Success... at last!
I did download the correct stock ROM (including boot.img, recovery.img and system.img). It was found as XAR-T580UEU1APG1-20160905144918.zip located HERE. This is the correct stock ROM for this device.
Before trying any of these steps, make sure you have installed the latest Samsung drivers. It may take a few minutes during some of these steps for the drivers to install. If at any point during these steps Windows has a notification that it is installing drivers, stop and wait until the drivers are finished installing. I noticed that a "Gadget Serial" installed when I connected my tablet to Odin in Download Mode. If that happens it's fine, let the drivers install before moving forward. Also it should be noted that this was performed using a PC with Windows 7 Professional.
COME WITH ME ON MY JOURNEY TO FREEDOM!
1. Boot in stock recovery
Hold Volume Up button + Home button + Power button
-OR-
Power off, wait for battery charge screen to come up, the hold Volume Up button + Home button + Power button
2. Wipe data & Factory reset
Press the Volume Down button until wipe data/factory reset is selected (highlighted/colored), then press the Power button, on the following screen use the Volume Up button or Volume Down button to select Yes and then press the Power button, once your screen is back on the main screen where you started, continue to step 3
3. Boot to Download Mode from stock recovery (do not boot to Android OS)
Press and hold Volume Down button + Home button + Power button
4. Odin, prep for flash and connect tablet (latest version, v3.12 at the time of this posting)
Open Odin and click options, then uncheck Auto reboot, and finally plugin your the USB cable into your tablet and PC. Once Odin recognizes your tablet, the far left box under ID:COM will turn blue and the Log tab will say "Added!!"
5. Flash TWRP custom recovery (twrp-3.0.2-0-gtaxlwifi.img.tar)
Click the AP button and find where you saved the TWRP zip.
Once the box next to AP is checked, click Start, if successful the Log will say "Successful 1 / Fail 0".
If this was successful, move on to step 6. Note that you don't have to unplug your tablet from the PC, just close Odin.
6. Boot to TWRP recovery (do not boot to Android OS). This step can be a tricky one and requires good timing. It is important to do these steps quickly.
From Download Mode, press and hold the Volume Down button + Home button + Power button (the Download Mode combo) until the screen goes black, then immediately press and hold the Volume Up button + Home button + Power button (the Recovery mode combo). You must switch from the Download Mode button combo to the Recovery Mode button combo before the Galaxy Tab boot screen appears. If you're too slow, you will have to go back to flash the stock ROM back to the tablet and start back at step 1.
Once in Recovery Mode, swipe the bar at the bottom of the screen, tap mount, and verify that the box next to Data is checked. Once that is verified, you can flash the SuperSU (SR4-SuperSU-v2.78-SR4-20161115184928.zip).
If you had not already copied it to your tablet, you can do this now since Windows should recognize it and allow you to copy the zip file to the table. You can also copy it to the external SD card if you have one and flash from there.
Once you have the SuperSU on your tablet, tap install from the main TWRP screen and then find it (you may have to search the folders), tap on it, and then tap install. If you are wanting to flash Xposed (xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip), or the boot image patcher (no-verity-no-encrypt_ashyx.zip), do not check the reboot box. Just swipe and flash SuperSU. Once done, go back and select the Xposed zip and flash. Once it is finished, go ahead and reboot, unless you also want to flash the boot image patcher to remove encryption. If you do, install, flash, and then reboot system.
NOTE: If you are going to flash all 3 (SuperSU, boot image patcher, and Xposed) do them in that order.
7. Confirm your work
Once Android is booted, check the SuperSu app and you'll verify you're rooted. Go ahead and reboot into TWRP recovery and you're Data partion is mounted and unencrypted. Now go ahead and install Xposed Installer (XposedInstaller_3.1.1.apk) and you're ready to download and use Xposed modules.
I followed these steps and have my Samsung Galaxy Tab A 10.1 (2016) (Model SM-T580NZWAXAR) rooted, unencrypted (data partition mounts in TWRP recovery), and Xposed framework installed flawlessly with no boot loops, no lost Data partition, no Encryption errors, and no hassel. All credit for the mentioned files and part of the steps to achieve this go to those that the credit is due. My contribtion is merely my journey and this 5 times tested, yes, I completely wiped and formatted my entire device and did this method 4 more times after I had success before writing this, to help others that might be frustrated for days as I was.
:victory:FREEDOM!!:victory:
Thanks for this, I'll be looking to root my tab after the holidays.....:fingers-crossed:
Hello!
Would someone be so kind and explain the following sentence to me:
tpsped said:
If you're too slow, you will have to go back to flash the stock ROM back to the tablet and start back at step 1.
Click to expand...
Click to collapse
Why should it be necessary to flash the whole ROM again?
I know that many ROMs reset the recovery to default, if TWRP hasn't patched the system, but then it should be enough to flash the custom recovery again.
DЯΦ[email protected]П said:
Hello!
Would someone be so kind and explain the following sentence to me:
Why should it be necessary to flash the whole ROM again?
I know that many ROMs reset the recovery to default, if TWRP hasn't patched the system, but then it should be enough to flash the custom recovery again.
Click to expand...
Click to collapse
When flashing the custom recovery, your Data will be unencrypted until you boot to Android OS.
In order to have an unencrypted Data partition, you have to follow these instructions in this order. If you are too slow and boot into the Android OS, you have missed the step and Data will become encrypted. Going back to Stock will once again reset the Data partition to unencrypted in order to properly make it permanently unencrypted.
Anyone unencrypted Data partition is needed in order to flash SuperSU, Xposed, the unencrypted method, or anything else in TWRP. The only exception may be flashing from external sd.
Anyone can correct me if I'm wrong, but I believe this should answer your question.
Wow thank you worked so well best of all guides
tpsped said:
Going back to Stock will once again reset the Data partition to unencrypted in order to properly make it permanently unencrypted.
Click to expand...
Click to collapse
To achieve this it is sufficient to format data partition in TWRP before flashing files, see https://forum.xda-developers.com/ga...ifi-galaxy-t3437666/post68154208#post68154208
ThemGo said:
To achieve this it is sufficient to format data partition in TWRP before flashing files, see https://forum.xda-developers.com/ga...ifi-galaxy-t3437666/post68154208#post68154208
Click to expand...
Click to collapse
Thanks for the info. I do welcome improvements to my instructions. I want to emphasize that these steps were the steps I took and that I figured out these steps on my own because there were no other instructions available that I could find. I'm always learning and growing!
tpsped said:
I'm always learning and growing!
Click to expand...
Click to collapse
Me too, I think everyone should :highfive:
Thank you for your guide, I like the clear steps.