Related
I got myself a bricked OV, was able to fastboot and flash new images.
Now it boots up directly to Android System Recovery, from where I got a copy of a stock nandroid backup.
When I first tried to restore, it said to go to adb and run nandroid-mobile.sh, couldn't figure out how to get it to work from within adb shell.
Then I formatted the SD card as FAT32, put the nandroid backup, back into it.
This time the restore worked. After select this directory, it goes
Restoring: ..............................................................
It's been about 10min and the dot just keeps moving. None of my other phones have taken this long.
I followed method 1 on this page to get new images flashed.
http://androidforums.com/optimus-v-...-optimus-v-rooting-roms-tutorials-thread.html
I tried flashing the stock ROM on the next post, which didn't do anything either. Kind of stuck on what I'm supposed to do at the moment.
Any suggestions?
Hrm I flashed CWM instead and ran the same nandroid backup.
It worked this time, but when I do a system reboot, it still just goes directly to recovery.
Well all I had to do was flash the Xionia Recovery from
http://forums.androidcentral.com/op...st-boot-loop-issues-caused-factory-reset.html
and it fixed itself at this point.
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.
I created this thread because I have looked all over and have been unable to find someone with the exact same issue(s).
I said "sort of" in the title because twrp is working. Ok, so before everyone asks if I have nvflash, the answer is no. I did not have the right version of firmware, and did not try to install it originally. Since I was able to install roms, I figured I was fine...oops.
Twrp is not properly installing roms. More on that later. I am getting to the asus splash screen that says my device is unlocked, but it is stuck there.
My last working rom was the deodexed stock JB rom from craig gomez. I installed it with goo and when I installed that, I lost custom recovery and root, so I decided to go back to a more custom rom so Titanium backup would work. When I did that, I tried also tried again to make nvflash work. I got through the first step, it said it was successful, except I never got the little message in the upper left corner that I was supposed to get. I did not think it was a big deal because my prime would still boot like normal.
Then I installed twrp 2.3.1.0 and I have tried flashing previous restore images. I have tried installing the roms on my sdcard. I cannot get past the asus splash screen.
If I try installing a rom with the force md5 check enabled, it does detect an md5 and then quits.
If I try intalling a rom without the force md5 check, i get an error that says E:Unable to mount '/staging'
When I try installing a backup everything seems to work okay, but then I get the same error E:Unable to mount '/staging'
When I try to install roms through fastboot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I try using adb, I do not see any devices.
I tried putting CWM on the prime to see if I could install from that instead, but it would not load after install.
I tried putting an older version of twrp on the prime, to see if that was the issue because I used to have an older version...I could not get that to load either...so I went back to this version.
Any ideas or suggestions would be awesome guys. I am stuck.
I even went to install the naked drivers again, and when I try to flash a different recovery, I get the <waiting for device> text that never goes away.
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
godlyitem said:
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
Click to expand...
Click to collapse
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
big time noob said:
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
Click to expand...
Click to collapse
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
godlyitem said:
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
Click to expand...
Click to collapse
Yeah, I thought that too, but fastboot does not work properly either...argh. I wish one of the gurus would chime in here.
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
Click to expand...
Click to collapse
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
godlyitem said:
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
That doesn't really help us. If possible, can you edit/delete your message so that the guys that might help do actually help? Don't want them to think this is done.
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
Click to expand...
Click to collapse
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
godlyitem said:
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
Click to expand...
Click to collapse
big time noob said:
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
Click to expand...
Click to collapse
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Thanks. That is what I needed to know.
I will see if I can make this work when I get back from work.
godlyitem said:
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Click to expand...
Click to collapse
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
Download the zip:
http://goo.gl/hiFHB
Goto to Twrp recovery and install the zip..Since it supports microsd u can transfer the zip to microsd.
Goto TWRP -> INSTALL -> CHOOSE EXTERNAL SD -> INSTALL THE ZIP
It will completely wipe the internal storage and then download the official STOCK JB FROM ASUS SITE and follow the same steps to install. Now install the latest twrp recovery using fastboot
big time noob said:
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
Click to expand...
Click to collapse
When I was doing the fullwipe the same errors happened to me.. But dont mind..I got errors like
1. No md5 file found
2. Mount error
3. Cannot find /staging
Just follow the above the steps ull get it right
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Yeah, I should have said I tried that first. I also tried the stock rom from asus. When that didn't work, I tried the stock rom deodexed I found in goo.
There are a bunch of permission errors going on inside my prime. When I go into the mount area, it will not let me mount the data to move it. Or, when I try to copy it over I get a failed message.
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Fixed?
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
big time noob said:
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
Click to expand...
Click to collapse
big time noob said:
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
Click to expand...
Click to collapse
You will have the jelly bean bootloader now so as long as you stick to it you should be fine. The only other thing I would suggest is check you version of twrp, you should be running the jelly bean version of it also. And if I am not mistaken, you need to be on ics to use nvflash (although I haven't checked the op recently so I could be wrong) so definitely stay away from that unless you downgrade.
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
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.