Evo 3d softbricked? - HTC EVO 3D

After I tried to backup my data and it got to the "backing up system" stage of the nandroid backup, my the progress bar was empty, and didnt load anything for like 3 min. I tried to flash a rom after a 3 times wipe, and same thing, at the flashing progress bar didn't load anything at all. I pulled the battery since it hadnt loaded any progress, but now I bootloop. I can still access my recovery menu and fastboot, but just cant boot up correctly. Im afraid that my recovery wont work if i try to flash a different rom. Anyone having the same problem, or solutions to this problem?

Ryoma Echizen said:
After I tried to backup my data and it got to the "backing up system" stage of the nandroid backup, my the progress bar was empty, and didnt load anything for like 3 min. I tried to flash a rom after a 3 times wipe, and same thing, at the flashing progress bar didn't load anything at all. I pulled the battery since it hadnt loaded any progress, but now I bootloop. I can still access my recovery menu and fastboot, but just cant boot up correctly. Im afraid that my recovery wont work if i try to flash a different rom. Anyone having the same problem, or solutions to this problem?
Click to expand...
Click to collapse
Get into fastboot. Run command "fastboot erase recovery" . Then go download the latest twrp.img , place this in your platform-tools folder or wherever fastboot is located. Then manually flash recovery "fastboot flash recovery twrp.img" reboot the phone into bootloader then go to recovery. Go to wipe and do a data wipe. Then to the advanced menu and format the system partition. Then download preludedrew stock rooted rom , and try to flash that. You should be golden.
Sent from my PG86100 using Tapatalk

Would that be this rom? http://forum.xda-developers.com/showthread.php?t=1192670
so i should navigate in terminal (i prefer to use my mac if i can) to platform-tools and type in ./adb devices
./fastboot
./fastboot erase recovery
./fastboot flash recovery twrp.img
Then wipe data and system partition from the epic win recovery, and flash the rom from the link above?

Please confirm if that's correct, if not, please tell me where im wrong.

Yeah the problem (really my bad i gotta delete this thread) was that the progress wasnt really shown, the previous recoveries i had used had shown progress continuously, but on the evo i just waited the full normal time it would take to install the package, and then the install completed itself instantly (nearly instantly).

Ryoma Echizen said:
Yeah the problem (really my bad i gotta delete this thread) was that the progress wasnt really shown, the previous recoveries i had used had shown progress continuously, but on the evo i just waited the full normal time it would take to install the package, and then the install completed itself instantly (nearly instantly).
Click to expand...
Click to collapse
Is it all working?
Sent from my PG86100 using Tapatalk

Just FYI
Some rom will not display progress bar correctly.

Related

How to solve Magic Value Mismatch. Solution Here!

Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilà... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method

SOLVED - Did crap hit the fan?

Hey everyone, I'm brand new to this, and I was told before I start getting into ROMS that I need to run this software:
http://forum.xda-developers.com/showthread.php?t=1182871
So I followed each and every step, and my phone rebooted and it said "Unlocked" like it was supposed to. BUT, when it booted into the OS, it booted into the stock OS as if I had just bought it off the shelf. Additionally, I am seeing a little exclamation point and android character when I go to the Android Recovery option under fastboot (also installed via linked software)
What happened!?
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
ravilov said:
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
Click to expand...
Click to collapse
I thought when the phone rebooted after unlocking bootloader, it would boot back into the system I had before unlocking it? I flashed the "Tenfar recovery" that was in the automated script. However, when I flashboot into "Android Recovery," this is when I get to the exclamation point/ android character. Is this normal?
EDIT: I just reran the script to install recovery, and it seems to have worked the second time. I ran a backup and saved it on my external SD card, but is this backup of MY system, or of whatever its now booting into after being unlocked?
Ok guys, apparently I've somehow managed to screw this up. I swear I am following instructions completely!
I decided to try MIUI first, and so I made the backup, wiped all the data/cache/etc, and flashed the ROM. Upon reboot I discovered I couldnt get past the Dual Core screen. So, I rebooted into recovery and flash my backup, and have now found out that I cant get past the "Rethink Possible" screen.
Since at that point you haven't flashed anything else yet, the backup you made couldn't be anything else but your "normal" system.
No idea what (if anything) might've gone wrong, but here's something that you maybe didn't know - after flashing a new ROM, the following boot will always take MUCH longer than usual. After that the phone should boot at "normal" speed again. So have patience and give it time.
Also, not sure how come you're stuck at "rethink" screen. As far as I know that's the very end of the boot process, it is shown just before the launcher starts. Still, give it more time. If nothing happens after, say, 5 mins, try booting into recovery and wipe data and cache, then try booting normally again.
I think I may have found the problem. When I go to restore, it runs for a while, and then says "Error formatting /data"
What should I do?
Alright, im at a loss here. I've done everything I can think of. I've tried every restore setting possible, I've wiped everything MANY times, I've flashed a few diff ROMS to try to get ANYTHING to work.
I am utterly confused about why none of this is working. I've read so much info on the forums that my head is just swimming. I never thought this would be that hard.
At this point I'd just like to get ANYTHING working so that I have a usable phone tomorrow.
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
i would add wipe all (data & cache) again after installing!
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
If that doesn't work either, here's an alternative method to wipe /data from recovery using adb.
When in recovery, connect the phone to the computer and run this:
Code:
adb shell
That should place you in the phone's shell. Now in recovery go to Mounts and storage > Mount /data.
Then in the phone shell (on the computer) run this:
Code:
mount | grep /data
It should print something like:
Code:
[color=red]/dev/block/mmcblk0p[B]XX[/B][/color] on /data type ext3 (rw,nodev,noatime,nodiratime,errors=continue,data=ordered)
Note the first value printed. For me it's /dev/block/mmcblk0p16 but I'm not sure if that goes for all Atrixes out there, so better safe than sorry.
Now go back to recovery and select Mounts and storage > Unmount /data.
Now back to the computer - run this:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p[B]XX[/B]
Where XX is obviously what you got from the previous command.
When it's done (you get your prompt back), type exit and go back to recovery on the phone. Now you can try restoring your backup or flashing a ROM or whatever.
Solved
barry_ said:
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
Click to expand...
Click to collapse
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
gianluca.tomat said:
i would add wipe all (data & cache) again after installing!
Click to expand...
Click to collapse
No luck im afraid.
ravilov said:
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
Click to expand...
Click to collapse
How do I do this on the computer? What do I type it into?
wvcaudill2 said:
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
Click to expand...
Click to collapse
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
harishatrix said:
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
Click to expand...
Click to collapse
How do I enter these flashboot commands into the computer?
wvcaudill2 said:
How do I enter these flashboot commands into the computer?
Click to expand...
Click to collapse
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
harishatrix said:
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
Click to expand...
Click to collapse
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
wvcaudill2 said:
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
Click to expand...
Click to collapse
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
harishatrix said:
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
Click to expand...
Click to collapse
Could you link me to these "fruitcakes," and do I flash them like everything else?
wvcaudill2 said:
Could you link me to these "fruitcakes," and do I flash them like everything else?
Click to expand...
Click to collapse
Here you go http://forum.xda-developers.com/showthread.php?t=1163009 and yes you have to flash it like all other roms.

[SOLVED - see 2nd page] Recovery problems - unable to boot into TWRP, CWM fails

Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Seleren said:
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Click to expand...
Click to collapse
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Lucky Thirteen said:
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
Click to expand...
Click to collapse
I have the International model.
jbharbin said:
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Click to expand...
Click to collapse
Tried that already, nothing changed at all, TWRP logo shows up and then the phone reboots to ROM. CWM works partially as I said, it reboots when I tell it do do anything (backup/wipe/flash) and the phone is unaffected.
Bump. Help please, I tried flashing another kernel but that didn't help. I can't even wipe or flash another ROM in CWM.
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Try redownloading the recovery and rewriting it. It may be a bad download.
Sent from my One X+ using xda premium
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Flash the kernel and then the recovery with fastboot and see what happens.
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
@Seleren I would be interested to know if the above worked for you? Also useful if anyone else gets this problem
Lucky Thirteen said:
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
Click to expand...
Click to collapse
I've already tried that numerous times, I can get to erasing cache etc but once I try to boot into the recovery ... I'm done. TWRP won't boot even after erasing cache. CWM fails at wiping/backuping/flashing and just reboots without any notice at all. I'm really out of ideas now.
Sorry for a bit late answer.
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
Seleren said:
Hello there,
... A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery....
Click to expand...
Click to collapse
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Lucky Thirteen said:
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Click to expand...
Click to collapse
Yes, I am correctly rooted, I've rooted numerous phones, I unlocked using the official HTC method. I could say I'm not a complete noob to Android. I wouldn't even post here if I didn't try all the standard procedures.
I flashed the Non-touch CWM yesterday and nothing changed (not that I expected it to). I decided I'll try flashing the bootloader in the end but I have to back up my whole SDCard before that ...
Bump.
SALVATION
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
hukel56 said:
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
Click to expand...
Click to collapse
wut?! TWRP = Recovery
boot.img = KERNEL
Seleren said:
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Click to expand...
Click to collapse
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Lloir said:
wut?! TWRP = Recovery
boot.img = KERNEL
Click to expand...
Click to collapse
Yea idk. But this happens
Lloir said:
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Click to expand...
Click to collapse
I wish that was the problem, I tried quite a few versions, including the one from ALL IN ONE toolkit, an older version that previously worked, the latest version and the ViperX version. Trust me, that was not the problem.
hukel56 said:
Yea idk. But this happens
Click to expand...
Click to collapse
What Lloir meant to say was that the boot.img has nothing to do with the recovery, so flashing a boot.img will NOT change your recovery to so-said TWRP.
TWRP is being flashed by a different command namely 'flash recovery' instead of 'flash boot' like previously mentioned boot.img

[Q] Trouble updating TF201 to KitKat

I'm hoping that some kind soul can help me. I'm about 10 hours into trying to update what was a stock TF201 to KitKat or possibly Lollipop.
First, I unlocked the TF201 using the official unlocking app supplied by ASUS. I didn't attempt to root as I figured I could flash a ROM that was already rooted. I then installed ADB and Fastboot on my Win7 PC. I had a bunch of trouble getting ADB and Fastboot to work reliably, but after trying a number of different things, I eventually got them both working reliably. I am currently using what I believe is the stock ASUS bootloader (<1.00 e> released by "WW_epad-10.4.2.15-20120917" A03). Next, I finally got CM Recovery 5.8.3.4 installed and working. I tried to flash a couple of different CM ROMs (cm-9.0.0-tf201.zip, cm-9.1.0-tf201.zip, and cm-11-20140926-UNOFFICIAL-tf201.zip), all with the same result. They appeared to install correctly, but upon reboot, they would all hang indefinitely at the initial ASUS splashscreen that says "The Device is UnLocked" in the upper left corner. I tried leaving the tablet alone for up to an hour in hopes that it would eventually start, but no luck. I have a feeling that the current bootloader I'm using is incompatible with the various OS images that I tried to install, but I could obviously be wrong. Can anyone tell me what I'm doing wrong or if there's a different bootloader I should be using?
Thanks in advance for your help!
Please ignore this last post. Somehow I got it working. I wish I could share, but I really don't know how or why it started working again.
I had the same problem after flashing cm 11 to my tf201.
(i followed the guide to make my tf201 "unbrikable" by backing up blobs via nvflash.)
i thried a lot of things to get cm running, but then i choosed "wipe data" in the bootloader menue. after that my tf201 doesn't start at all.
i can see the android robot and a blue status bar for 1 second, then screen turns black 1 second, then the android robot comes back and so on. i can't stop this loop. Pulling down the power button simply starts this process new. can't start bootloader o.e.
What have i dun?? -.-
negRomino said:
I had the same problem after flashing cm 11 to my tf201.
(i followed the guide to make my tf201 "unbrikable" by backing up blobs via nvflash.)
i thried a lot of things to get cm running, but then i choosed "wipe data" in the bootloader menue. after that my tf201 doesn't start at all.
i can see the android robot and a blue status bar for 1 second, then screen turns black 1 second, then the android robot comes back and so on. i can't stop this loop. Pulling down the power button simply starts this process new. can't start bootloader o.e.
What have i dun?? -.-
Click to expand...
Click to collapse
Just restore via nvflash ?
Thx Josh
lj50036 said:
Just restore via nvflash ?
Thx Josh
Click to expand...
Click to collapse
After a long time of hating myself for bricking the tf201 i am about to give a new try to reset via nvflash.
I read the tutorial (http://forum.xda-developers.com/showthread.php?t=1927818) but the attached files for unblobd stock ROMs or the semi-automated complete recovery are not online anymore. anyone who can help me out with the files?
edit: APX driver works.
negRomino said:
After a long time of hating myself for bricking the tf201 i am about to give a new try to reset via nvflash.
I read the tutorial (http://forum.xda-developers.com/showthread.php?t=1927818) but the attached files for unblobd stock ROMs or the semi-automated complete recovery are not online anymore. anyone who can help me out with the files?
edit: APX driver works.
Click to expand...
Click to collapse
If you dont have your blob.bin its pointless..
This file is from your device (needed backed up before a brick) and only for your device......
Thx Josh
do not use CM Recovery ......... USE TWRP
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
YOU HAVE TO FLASH BOOTLOADER ON THE LINK
https://www.androidfilehost.com/?fid=23060877490002899
Check MD5 FEEA44BC7370116E1807DC943E2700B5
unzipit and copy "blob" in adb/fastbooy folder
fastboot flash boot blob
than reboot
YOU HAVE TO FLASH RECOVERY ON THE LINK
https://www.androidfilehost.com/?fid=95916177934539154
Check MD5 118eb4f530c99922126d11f71c981429
unzipit and copy "boot.blob" in adb/fastbooy folder
fastboot erase recovery
fastboot flash recovery boot.blob
reboot
Go to twrp/wipe/format data then type yes
It takes about 70 minutes to format
Make sure that your battery is full
Do Not interrupt format(if you do, it will brick)
After it's done go to Wipe//Advanced Wipe//Select Data
Tap “Repair or Change File System”//”Change File System//F2FS
Swipe to Change
Wipe dalvik cache, system, cache, data, internal storage
Flash KatKiss-5.1.1_TF201_030.zip from microsd card
Flash Supersu.zip
Flash Gapps.zip
Reboot

Can't install recovery on slot A

EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.

Categories

Resources