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.
Related
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Use this thread to install CWM, I'm not a fan of TWRP. http://forum.xda-developers.com/showthread.php?p=25786947 I used this and had no problems updating
Sent from my NOOK Tablet running CM10
deltantor said:
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Click to expand...
Click to collapse
This has been happening to me occasionally. I have found that when I get the black screen, pressing the Power button launches Recovery (CWM in my case). See if that works for you.
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
To the rescue
Ok, I have posted this on a different day. Try this with a blank sd card. Look at the bottom post called "Here is a video"
It a external boot cwm v.5 but you can copy this into your sd then flash and you have cwm v6.0.1.5 internal. Either way you have two ways to do recovery (external and internal):victory:
djd338 said:
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
Click to expand...
Click to collapse
Thanks very much for the reply & link!
I'll do this ASAP when I get back home & report. Thx again!
Sent from my Nexus 7 using Tapatalk 2
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Look pass the fear and go one step at a time, before you know it, your there.
It looks like you have already resolved this from this thread.
Ok, basically I'll go step by step.
1. Download ubuntu iso from ubuntu website (you can donate or put 0$ then download iso) and burn it to cd. 5 minutes
2. Stick the cd into a system that you don't plan to look at the video that is showing you the process and boot it up from a reboot and not from within windows. Select the left square which basically load the ubunbu from cd but does not install anything to your hard drive.3 minutes
3. You can view the whole video but I would skip to the section in video (3:28 watch to 4:43, 6:56 watch to 8:06 ) where I mentioned the setting the two flags in your sd after quick format fat32 and extracting the four files into your sd within ms windows platform from the post . I did this with a normal mini sd card adapter and not the usb stick adapter he used in the video. Since you are doing this to a blank mini sd then there really nothing to worry about since it is blank in the first place. 2 minute
4. If you had your apps backup with titanium backup then it still will be on the main mini sd and not the one that working with for this recovery.
5. I notice you did not mention wipe dalvik cache from your post. You should always wipe dalvik then wipe factory then do a single flash to test boot up.. You can flash gapps after a successful boot up into jellybean. (here's a video showing that I'm using external cwm v.5 even though its recommended to use v.6 .) You can always use cwm v.6 on your next cm10 test rom or use cwm v.6 to reflash to same rom once a successful boot up have been obtained with external cwm v.5. This purpose is to get it running on your nt.
6. Be patient for the first boot. Should not be more than 5 minutes max. It will look black then load. If it boot loops then wipe dalvik then wipe factory and do a single flash to test boot up again.
This will at least get cm 10 flavored rom on to your nt.
djd338 said:
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Click to expand...
Click to collapse
Got it back! Thank you for your help & patience. Also for the timely responses. I now have a bootable "recovery sd card" for curing these type problems. I've labeled it & filed away for any future borks of this kind! And I have cm10 up & running stable.
Thank you!
Sent from my Nexus 7 using Tapatalk 2
Okay my Atrix 4g has unlocked bootloader, Android 2.3.6, and I flashed CWM recovery the other day, and it worked fine except whenever I plugged in my phone to wall charger, it would boot AUTOMATCALLY into that recovery. Followed this guide: LINK
I then installed CWM recovery 5.0.2.3 from here: LINK
Now again when I plug usb into wall to charge, it boots into the first recovery I installed. I can't see the battery charge symbol.
Now I downloaded this ROM - http://forum.xda-developers.com/showthread.php?t=1836674 and tried to boot into recovery from using the volume down button until "Android recovery" but that takes me to the stock 4 option crap.
So I tried to flash the MROM from ROM manager in the os, and it says restarting into recovery, AGAIN that takes me to the triangle exclamation point crap.
SO MY QUESTION is if I do a disk clear, format from the recovery, would my phone still work with T-mobile afterwards, and I can install the CWM again, and flash the new ROM?? I don't care about losing data, I have only few apps.
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
ravilov said:
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
Click to expand...
Click to collapse
Here's a crazier idea - do you mind explaining things in more detail, since I am a noob and this is a help forum.
--
When I install the the recovery, it just says hit yes to continue. Please help, rather than telling me that I am an idiot.
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
ravilov said:
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
Click to expand...
Click to collapse
No problem mate.
Well I guess I could tell you what I did, but I did exactly what the guides said:
downloaded the .zip archive, placed contents anyplace, and started cmd from that folder and entered:
adb install MOTOA4_Bootstrap_0408_1720-signed.apk
Then I opened up that app "System Recovery" and hit Install recovery, then I hit recovery mode from the app, and was told to connect the usb to the wall charger, not pc. And that was it for the first recovery. I then noticed that this specific recovery was missing some functions in the actual recovery so I installed 5.0.2.3 later.
I downloaded the .zip from the site and placed inside phone internal SD, the second link from OP here, turned on phone and went into Android recovery and it opened up the one I installed just a minute ago, and hit install zip from sdcard, I hit internal, and selected the .zip I downloaded from that site. I hit reboot recovery and it booted into that recovery, 5.0.2.3, the real one.
To go to this new one, I insert wall usb to phone and it boots in the first recovery, and I hit, reboot recovery, and it takes me to the new one.
NOW whenever I plug in usb to wall to charge, it boots in the old recovery, and I don't see charge symbol. I have calibrated my battery 3 times, and it is still CRAP (brand new 1800mah battery for mb860).
Anyways, I thought to ask here if I did a wipe data from the new recovery, or old, would it get rid of this whole mess?
Hmm ok.
I told you this before but here goes again. I'd give up on random guides from random sites. Everything you need is right here on this forum.
Not to mention, the recovery in that ZIP is slightly older, there is a newer one available.
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
The ZIP you downloaded seems fine, but it's somewhat likely your boot is also messed up too. If all this goes well, you can try finding the T-Mobile fruitcake (go over to the Atrix Reboot Project thread) and flashing it from the recovery. Be aware though that you might lose all data in doing this.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
ravilov said:
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
Click to expand...
Click to collapse
ALRIGHT thanks for this actual guide.
It installed fine, works fine, AND AGAIN whenever I plug the wall charger in when the phone is off, it boots into the OLD OLD recovery, from the first link.
I still can't see the battery.
Please stop throwing sass at me. :crying:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
ravilov said:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
Click to expand...
Click to collapse
I can only find this: http://forum.xda-developers.com/showthread.php?t=1163009
I downloaded the 2.3.6 ROM from the backup thread. Says nothing about T-mobile.So do I just install this from the new CWM?
Is there just no way of getting rid of CWM recovery so I can install it just once, rather than you keep telling me to install this and that?
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
ravilov said:
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
Click to expand...
Click to collapse
YES!!! Because everytime I connect the damn charger it boots cwm. AND EVERYTIME I hit ANDROID RECOVERY I boot into the OLD OLD OLD OLD Recovery.
why is that hard to understand? I want to uninstall ALL the cwms, and install the one you sent me just to have that one, rather having 3 different cwms I have right now.
Also that thread is just a bunch of people talking about nothing really. HAS ABSOLUTELY nothing to do with T-mobile whatsoever.
I just want to make sure that this AT&T phone will still work with my t mobile sim card after I install ROMs!!!!
---
And for the love of all that is holy, don't reply with: "why won't it?"
BECAUSE THAT IS WHY I AM ASKING. I have never done this, that is why I ASK!!!!!
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
ravilov said:
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
Click to expand...
Click to collapse
SO there is NO WAY to remove CWM recoveries?????
LOL THIS IS FUNNY! Now when I plug charger in, it just boots into OS, and when I hit android recovery with VOL buttons, it shows the white triangle.
Still don't get what that rom did. Installed it, and nothing, except for losing all my data.
This forum made things worse.
Thank you.
EDIT: OKAY NOW it shows the battery when plugged in but still the white triangle crap in the recovery.
You must have SOME recovery. You can install TWRP if you like that better, but you must have SOMETHING. By following the procedure I described you properly installed RomRacer's CWM so that part is fine. Now, why are you still sometimes getting the stock 4-option recovery - only heaven knows.
I don't think there's a way to install the stock Motorola recovery other than installing the full SBF, however SBFs are VERY dangerous and nobody is going to recommend that.
I really can't imagine what you've done with your phone. The mere fact you have multiple recoveries raises a big red flag right there. I tried to help the best way I can, but since obviously it's not doing much good, I'm going to refrain from further comments and let someone else take over. Good luck.
Ravilov has said it all but its pretty spread out trying to figure out what happened so I'm hoping I can tie it all together.
If you attempt to boot into recovery and get the old android recovery but booting normally puts you into CWM Recovery then somehow you have flashed the BOOT partition with CWM image. To fix this just download the correct fruitcake and flash the BOOT.IMG to the BOOT partition using the moto-fastboot tool and reboot. I would recommend erasing the BOOT partition first just in case.
Sent from my Nexus 7 using xda app-developers app
Thanks for your patience and help Ravilov
Sent from my MB860 using xda app-developers app
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Vant2239 said:
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Click to expand...
Click to collapse
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
robneymcplum said:
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
Click to expand...
Click to collapse
Once again thanks a lot for reply!
I have successfully ported one of your builds, but with some mindless actions trying to flash recovery through fast boot got a boot loop of some sort, logo keeps appearing and phone doesn't boot.
What I did is in fastboot flashed recovery with help of 'fastboot oem unlock' and now I just stuck. I have stock recovery, tried to flash it back but unsuccessfuly. Any idea how can I fix it?
Sorry for being such a noob
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
robneymcplum said:
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
Click to expand...
Click to collapse
Im getting an error when try to flash it: ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
trying to flash stock firmware?
I had numerous issues getting mine to flash the first time, I downloaded and tried different versions of SPflash tools, different USB leads/ports etc...
I have to use a USB lead from my moto x play as the stock lead wouldnt work, my galaxy tab lead wouldnt work either.
I have to use SPflash tool version SP_Flash_Tool_exe_Windows_v5.1552.00.000 as other versions kept bringing up that error and similar ones.
It really does seem to be trial and error unfortunately.
Hello,
I got a little problem with my lg g5.. I've unrooted my phone for a couple weeks ago to try and update to the latests version of android but I'm stuck at the part of updating.
Currently my phone is running android version 6.0.1 but I've seen that there is a newer version and I would love to install it on my phone but the notification that is popping up every day is nog working.
Hope somebody can help me.. Im really bad at this kinda things.
Do you have TWRP installed as a custom recovery? If so I understand your need to flash the default recovery img or updating from the phone will fail on reboot.
Check our autoprime's all in one guide that might help you troubleshoot and restore your phone to MM or N
megatron_lives said:
Do you have TWRP installed as a custom recovery? If so I understand your need to flash the default recovery img or updating from the phone will fail on reboot.
Check our autoprime's all in one guide that might help you troubleshoot and restore your phone to MM or N
Click to expand...
Click to collapse
Is there a way to check what custom recovery I've installed? It's been a while since I rooted my phone..
Turn off the phone or remove the battery. Then, hold down the volume down button and then the power button. Keep them both held till you see the LG logo, then release the power button and briefly press and hold the power button again. If successful you should see a white, factory restore menu. Use the volume keys to navigate and the power button to select yes on both the two screens. NB if you do not have a custom recovery this will factory restore your phone-so make a backup. If you do have a custom recovery, it should boot up e.g TWRP
From here you can flash the default boot loader img and then update ota
megatron_lives said:
Turn off the phone or remove the battery. Then, hold down the volume down button and then the power button. Keep them both held till you see the LG logo, then release the power button and briefly press and hold the power button again. If successful you should see a white, factory restore menu. Use the volume keys to navigate and the power button to select yes on both the two screens. NB if you do not have a custom recovery this will factory restore your phone-so make a backup. If you do have a custom recovery, it should boot up e.g TWRP
From here you can flash the default boot loader img and then update ota
Click to expand...
Click to collapse
When I restart my phone and use those keys my phone is booting into the white screen where I can go into factory restore.. Do I need to install a custom recovery first?
Once in the white screen, to see if you do have a custom recovery installed, you need to select yes on both screens to enter the custom recovery. As I said before, if you do not have a custom recovery (such as TWRP) you will factory reset your phone and lose all settings so make backups first.
Before all that though, how did you root and into it your phone- that will give me an idea as to if you have a custom recovery installed
megatron_lives said:
Once in the white screen, to see if you do have a custom recovery installed, you need to select yes on both screens to enter the custom recovery. As I said before, if you do not have a custom recovery (such as TWRP) you will factory reset your phone and lose all settings so make backups first.
Before all that though, how did you root and into it your phone- that will give me an idea as to if you have a custom recovery installed
Click to expand...
Click to collapse
I've been using the bootloader unlock from this link
So you most likely flashed TWRP if you followed the instructions verbatim. How did in root?
megatron_lives said:
So you most likely flashed TWRP if you followed the instructions verbatim. How did in root?
Click to expand...
Click to collapse
Flashed the SuperSU with TWRP, it's down below at the tutorial page.
Now I only need to know what I need for the stock recovery and how I can update my phone
For the stock recovery, I have 6.01 10E stock recovery here https://drive.google.com/file/d/0B3j5Gs11w3EqVzNwa0h3b2tVWmc/view?usp=drivesdk
Hopefully that should work. If not, you can extract the recovery image from the full zips on autoprime's all in one LG g5 post.
Good luck
Hope I will get it working xD Thanks for your help!
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
el.quechon said:
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
Click to expand...
Click to collapse
You may have to LG UP and start over, also you can try one of the stock based roms.
Ainz_Ooal_Gown said:
You may have to LG UP and start over, also you can try one of the stock based roms.
Click to expand...
Click to collapse
how can i get in download mode everytime i try to power off it just reboots to twrp
el.quechon said:
how can i get in download mode everytime i try to power off it just reboots to twrp
Click to expand...
Click to collapse
There should be a option under reboot to just shut off does it try to reboot if you click that?
Ainz_Ooal_Gown said:
There should be a option under reboot to just shut off does it try to reboot if you click that?
Click to expand...
Click to collapse
yes and every options of twrp asks me if i want to install twrp app which is weird
So connecting usb cable, force resetting it, press combo for download mode (volume up + usb cable ?)
doesn't work ?
Or at least fastboot mode ?
connecting usb cable, force resetting it (vol down + power), press combo for fastboot mode (volume down + usb cable)
zacharias.maladroit said:
So connecting usb cable, force resetting it, press combo for download mode (volume up + usb cable ?)
doesn't work ?
Or at least fastboot mode ?
connecting usb cable, force resetting it (vol down + power), press combo for fastboot mode (volume down + usb cable)
Click to expand...
Click to collapse
ill try letting it reboot with the usb cable and see what happens
when twrp reboots it doenst even show the lg v30 screen it just shows a black screen for half a second then it goet straight to twrp
edit: i restored a stock backup and nothing is there a solution that can be done from twrp terminal
el.quechon said:
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
Click to expand...
Click to collapse
that's the important part, I don't really know how much the t-mobile models differ from the H930 ones
but there should be fastboot ? download mode ? "factory reset" functionality (via button dance botting into TWRP) ?
el.quechon said:
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
Click to expand...
Click to collapse
You might have done what I did which is flash twrp.img in recovery.. it won't go back to initial password screen. I did that and had the same issues.. I recently did it.. now it only restores backups which is how I got lineage or other rooms back.. after wiping the system partition, it also only flashes stock debloated room, but anything else I flash crash system partition.. I'm going to start over but with treble recovery in root process and just avoid messing with it..
lowkeyst4tus said:
You might have done what I did which is flash twrp.img in recovery.. it won't go back to initial password screen. I did that and had the same issues.. I recently did it.. now it only restores backups which is how I got lineage or other rooms back.. after wiping the system partition, it also only flashes stock debloated room, but anything else I flash crash system partition.. I'm going to start over but with treble recovery in root process and just avoid messing with it..
Click to expand...
Click to collapse
i didnt flash recovery i was flashing the custom rom but if i restore a stock rom back up it doesnt work either
el.quechon said:
i didnt flash recovery i was flashing the custom rom but if i restore a stock rom back up it doesnt work either
Click to expand...
Click to collapse
Did you restores the recovery as well? I did that which is suspect source of the problem number 2.. even flashing magisk crash my system partition.. but not the magisk in the stock room, probably cause it's built in.. or any restores.. either way I'm going to start over.. not touching recovery after root & not backing up recovery partition to confirm a few things.. can you flash debloated rom after formatting system partition? Aroma gapps don't work for me but other gapps does.. I found out the hard way cause I didn't see any information on it in the threads.. I read it's a common issue with TWRP recovery on multiple devices..
lowkeyst4tus said:
Did you restores the recovery as well? I did that which is suspect source of the problem number 2.. even flashing magisk crash my system partition.. but not the magisk in the stock room, probably cause it's built in.. or any restores.. either way I'm going to start over.. not touching recovery after root & not backing up recovery partition to confirm a few things.. can you flash debloated rom after formatting system partition? Aroma gapps don't work for me but other gapps does.. I found out the hard way cause I didn't see any information on it in the threads.. I read it's a common issue with TWRP recovery on multiple devices..
Click to expand...
Click to collapse
Got it working luckily my phone was almost dead so once it died tarp started working fine so now everything is normal
el.quechon said:
when twrp reboots it doenst even show the lg v30 screen it just shows a black screen for half a second then it goet straight to twrp
edit: i restored a stock backup and nothing is there a solution that can be done from twrp terminal
Click to expand...
Click to collapse
I had that once when i tried to flash the aroma gapps for pie ?
that kinda ****ed up TWRP, a force reset (vol- + power) did the job for me, as all the reboot/shutdown options in TWRP didnt wanna work.
SGCMarkus said:
I had that once when i tried to flash the aroma gapps for pie ?
that kinda ****ed up TWRP, a force reset (vol- + power) did the job for me, as all the reboot/shutdown options in TWRP didnt wanna work.
Click to expand...
Click to collapse
Exactly what happens to me try the aroma installer from gapps project and everything went down hill now I flashed the stock one they have.
How can I delete Google apps installed by gapps without making other Google apps crash
Did you not have a backup of your rom using twrp before you made the change? Isn't that the whole point of having twrp and a phone with SD card? Always backup your whole phone before making a change. It has saved my phone many times.
Alibaba0101 said:
Did you not have a backup of your rom using twrp before you made the change? Isn't that the whole point of having twrp and a phone with SD card? Always backup your whole phone before making a change. It has saved my phone many times.
Click to expand...
Click to collapse
Yes I had a back up but it was twrp acting up by not being able to boot.
My phone was just booting back to twrp even when pressing power off some how by finally powering off the device (letting it discharge all the way) that was the only thing that fix it me twrp started working fine after that
My twrp has been acting funny/unpredictable. Or I am not doing something right. Mostly has to do with the restore function. I generally have two separate roms backed up in restore. But, lately, I will see only one listed. When I get back to the phone and check in my root manager, I will see them both listed. And then later, it (Rom) "might or might not" return to the restore function area.
But, lately it seems that when I restore the system, I can not open it up in the lock screen (does not recognize the pin). I have to turn the phone off, then use the vol down and power button to get back into twrp. Luckily, I have a couple of roms downloaded in the install section which then does let me flash and reboot, but I have to start new/over.
I don't know if reflashing twrp in recovery will help or not (have never done it).
I'm afraid one of these times I will some how get locked out or not be able to flash a good rom.
gimpy1 said:
My twrp has been acting funny/unpredictable. Or I am not doing something right. Mostly has to do with the restore function. I generally have two separate roms backed up in restore. But, lately, I will see only one listed. When I get back to the phone and check in my root manager, I will see them both listed. And then later, it (Rom) "might or might not" return to the restore function area.
But, lately it seems that when I restore the system, I can not open it up in the lock screen (does not recognize the pin). I have to turn the phone off, then use the vol down and power button to get back into twrp. Luckily, I have a couple of roms downloaded in the install section which then does let me flash and reboot, but I have to start new/over.
I don't know if reflashing twrp in recovery will help or not (have never done it).
I'm afraid one of these times I will some how get locked out or not be able to flash a good rom.
Click to expand...
Click to collapse
when it doesnt recognize your pin, go (in twrp file manager) to /data/system/ and delete the locksettings.db(-sh/-wal) files...
I think that was the path, you can google that too ^^
Thx, SGCMarkus, I did delete just the one db only file. It did away with the pin unlock code on reboot (but I did not do a restore, just a reboot back into my system), so I assume it will work. I will try it when I have time. I think that deletion has to be done everytime in twrp, because the line does reappear the next time I booted back into twrp?
Thx.