So I have a serious issue with my Sprint Hero. I decided I would try Firerat's custom MTD partition. Unfortunately my phone decided that it would not be recognized by ADB at all. So naturally I end up with the exact error Firerat said that I would get if I didn't reboot through ADB
9. Once its wiped, plug ur phone in and pull up command to adb reboot recovery (if you try to reboot into recovery any other way itll mess up the partitions and ull get cache memory.log errors and that will mean the mod didnt work correctly
Click to expand...
Click to collapse
Quoted from his thread. So I try not to panic and attempt to start over from step 1. Except now I can't do that because the error just keeps happening. So I decided to restore the backup I made before I tried all this. Except I can't because it tells me that I don't have enough memory to do that. So I decide to just install a fresh CM7. Oh wait, I can't do that either because it just doesn't install anything and after telling me that it successfully installed it, I wind up staring at a white HTC loading screen for a million years.
So basically my phone is completely effed. I can't use the RUU to revert to stock so I feel I'm kind of out of options. Please for the love of all that is holy help me fix this. (Which was caused by my own lack of experience and sheer epic stupidity, so I blame no one by myself.)
---------- Post added at 11:43 AM ---------- Previous post was at 10:57 AM ----------
Oh thank god for false alarms. After much work wiping and attempting to install I FINALLY got it working again. I panicked for nothing it would seem. Mods can close, delete, or whatever they want to do with this thread if they so deem.
For future reference, under the advanced section in a clockwork recovery is an option to reboot recovery. Use it instead of ADB, its much simpler.
Sent from my HERO200 using xda premium
how did you end up fixing it? im having a similar problem with my hero. i factory reset the device and the flash i was attempting failed. my phone only goes to recovery, hboot and get stuck on power on screen.
Good day all,
So last Lollipop ROM I played with (maybe rapture) I accidentally left the Reactivation Lock checked not knowing what it actually was. Upon trying to flash another rom I am welcomed by "Custom binary blocked by reactivation lock". I've tried recovery with Kies but I've never been able to get a code for it. And the serial of the phone doesn't work. I've tried to 'unroot' using stock firmware and Odin. But it bootloops up to the T-Mobile logo. Trying auto root fails thanks to the lock. I'll probably give Odin another shot and see if I can at least get it booted next. But at least I've removed signs of root so I can take it back to T-Mobile. But I'd rather get this fixed myself. Any suggestions?
After you Odin to stock lollipop.
Boot into recovery and factory reset / data wipe and it should boot up instead of bootlooping.
Happened to me once.
Flash latest twrp
Unchecked auto reboot
Pull battery out
Boot into recovery
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
SerialCynic said:
Good day all,
So last Lollipop ROM I played with (maybe rapture) I accidentally left the Reactivation Lock checked not knowing what it actually was. Upon trying to flash another rom I am welcomed by "Custom binary blocked by reactivation lock". I've tried recovery with Kies but I've never been able to get a code for it. And the serial of the phone doesn't work. I've tried to 'unroot' using stock firmware and Odin. But it bootloops up to the T-Mobile logo. Trying auto root fails thanks to the lock. I'll probably give Odin another shot and see if I can at least get it booted next. But at least I've removed signs of root so I can take it back to T-Mobile. But I'd rather get this fixed myself. Any suggestions?
Click to expand...
Click to collapse
Happened to me once
Download mode
Flash latest twrp via odin
Unchecked auto reboot
Pull battery out
Boot into recovery
The same thing happened to me here. I am following the directions posted to fix but flashing the recovery keeps failing. Please help
Edit: FIXED.
I had to Odin Cod6 stock to access my phone again. Soon as you get in, make sure you go to settings, security, and disable the lock. It will ask you for your Gmail account I believe.
Another "device is corrupted" message - Syatem files wiped
I have a real problem on my hands. Just got a new Nexus 6 and used the Nexus Root Toolkit to unlock and root and add TWRP. The process went smoothly until after TWRP install. I recall that from TWRP I was rebooting after installing Busy Box and SuperSU. On the reboot I got the dreaded “Your device is corrupted…” and the phone instantly shut down. Pressing the power button after that message does not work. I went back to the toolkit and tried everything (stock, unroot, etc.) and nothing worked. I've rooted a NOTE 2 a few years ago but I forgot most of what I learned.
I can however boot into recovery and bootloader mode. Also it looks like all system files on the phone got wiped. The problem is that my computer can see the phone's file system only when I'm in recovery, not when I'm on the bootloader screen. Any ideas as to how to fix?
Can I put an image file on a USB stick and install from recovery? Thanks for your help..
Use fastboot. Flash system and boot and recovery from bootloader. Adb doesn't work in bootloader mode.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 06:58 AM ---------- Previous post was at 06:55 AM ----------
Actually just boot the phone. The corrupted message will disappear and the phone will boot. After 30 or 60 seconds. I forget. The kernel sets the flag that you're on a modified recovery so the message displays. Nothing wrong with the phone. Your system is still there.
Sent from my Nexus 6 using Tapatalk
Also make sure you applied the latest SuperSU available plus the boot image
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i fixed that by flashing to factory firmware if you don't know how message me for steps
Installed TWRP 3.1.0. Can't boot into recovery. Hangs at "Your device is booting now.
Hi.
I have unlocked my P9 EVA-L09. Flashed TWRP recovery. Installed SU. Downloaded and installed Huawei P9 B383 Nougat update_data_full_hw_eu.zip. Booted into system, phone working perfectly, but NO ROOT. Flashed new recovery TWRP 3.1.0-0-eva. Turned phone off. Pressed VOL + and - and power until image appears. Screen changes to EMUI updater then gives error Software install failed.
Anyone help please?
Only V+ and Power. Your method starts dload.
dkionline said:
Only V+ and Power. Your method starts dload.
Click to expand...
Click to collapse
Same as before using Vol+ and Power. Still hanging at "Your device is booting now......."
Hold the keys until twrp comes up, if doesnt work, flash latest 3.1.0-2
salineBoy said:
Same as before using Vol+ and Power. Still hanging at "Your device is booting now......."
Click to expand...
Click to collapse
Does it boot into android at all? Or does it only hang when trying to boot recovery? If it's the latter boot into android and then power off and boot into android again.
Then power off and try booting into twrp. If that doesn't work download twrp again because you probably have a botched download.
If it doesn't boot into android then you will have to start again from full stock because you've soft bricked your phone.
Thread moved to Questions & Answers. Doesn't belong to Development.
dkionline said:
Hold the keys until twrp comes up, if doesnt work, flash latest 3.1.0-2
Click to expand...
Click to collapse
Thank you. Now able to boot to recovery! However, when I try and install SU (SR3-SuperSU-v2.79) via TWRP I hit a problem. I select the zip from internal storage and proceed to install . Phone reboots before completion. Have I the correct version of SU?
Regards
dkionline said:
Hold the keys until twrp comes up, if doesnt work, flash latest 3.1.0-2
Click to expand...
Click to collapse
Having manage to boot into TWRP once, subsequent attempts to boot to recovery bring me to EMUI erecovery. I have tried Vol + and Power key from reboot and from shutdown with no luck. I have flashed the recovery again (3.1.0-2), but get the same result.
Regards
Use SuperSU patched for emui5.
dkionline said:
Use SuperSU patched for emui5.
Click to expand...
Click to collapse
Think I'd like to get booting into recovery before I can install SU, or have I got this back to front?
Thanks
salineBoy said:
Think I'd like to get booting into recovery before I can install SU, or have I got this back to front?
Thanks
Click to expand...
Click to collapse
yes, no other options.
Sorry, I must be awfully thick, but I don't understand. What do you think I'm doing wrong?
Thanks
Got this exact same problem. Only one build of TWRP will boot correctly and reliably that's 3.1.0-2, any other versions at all, won't boot, so 3.1.0-0 for example doesn't boot.
---------- Post added at 06:36 PM ---------- Previous post was at 06:32 PM ----------
howsonph said:
Got this exact same problem. Only one build of TWRP will boot correctly and reliably that's 3.1.0-2, any other versions at all, won't boot, so 3.1.0-0 for example doesn't boot.
Click to expand...
Click to collapse
And I have a second problem on top of that which is mentioned in other threads. The touch screen doesn't work. I can see what's happening, but it won't respond to my finger. Using the power button locks the phone and I can't swipe to unlock because it doesn't respond to my finger. (TWRP does seem to be running OK, just not taking input from the touchscreen).
I see in other threads people have solved this one by changing their TWRP version, but since only one version works for me on this phone, I can't use that solution...
howsonph said:
Got this exact same problem. Only one build of TWRP will boot correctly and reliably that's 3.1.0-2, any other versions at all, won't boot, so 3.1.0-0 for example doesn't boot.
---------- Post added at 06:36 PM ---------- Previous post was at 06:32 PM ----------
And I have a second problem on top of that which is mentioned in other threads. The touch screen doesn't work. I can see what's happening, but it won't respond to my finger. Using the power button locks the phone and I can't swipe to unlock because it doesn't respond to my finger. (TWRP does seem to be running OK, just not taking input from the touchscreen).
I see in other threads people have solved this one by changing their TWRP version, but since only one version works for me on this phone, I can't use that solution...
Click to expand...
Click to collapse
It depends if you on MM EMUI 4.1 or N EMUI 5.01 - for the latter you have to use TWRP 3.1.1.-1 ported to Huawei P9 (not some who knows where from)
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better its extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
zgfg said:
It depends if you on MM EMUI 4.1 or N EMUI 5.01 - for the latter you have to use TWRP 3.1.1.-1 ported to Huawei P9 (not some who knows where from)
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better its extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Click to expand...
Click to collapse
Ah yes, I am on 5.01, that would probably explain it. I'll upgrade to the latest version and see how it goes, thanks for that.
---------- Post added at 07:52 PM ---------- Previous post was at 06:58 PM ----------
That version certainly works, although it still isn't responding on the touch screen for some unknown reason.
howsonph said:
Ah yes, I am on 5.01, that would probably explain it. I'll upgrade to the latest version and see how it goes, thanks for that.
---------- Post added at 07:52 PM ---------- Previous post was at 06:58 PM ----------
That version certainly works, although it still isn't responding on the touch screen for some unknown reason.
Click to expand...
Click to collapse
Touch screen in TWRP works fine for everybody. What is exactly your stock ROM and does it correspond to the builds as listed in the TWRP installation instructions I gave you
Only if you screwewd up something by using wrong TWRP
Can you boot to system?
Maybe you should flash stock eRocevery back, do Factory reset with cleaning Internal memory and flash proper TWRP again
zgfg said:
Touch screen in TWRP works fine for everybody. What is exactly your stock ROM and does it correspond to the builds as listed in the TWRP installation instructions I gave you
Only if you screwewd up something by using wrong TWRP
Can you boot to system?
Maybe you should flash stock eRocevery back, do Factory reset with cleaning Internal memory and flash proper TWRP again
Click to expand...
Click to collapse
Yeah thinking something like that. I've clearly screwed something up somewhere. I think as you say will probably sort it. Some combination of re-installing and resetting sorted it for other posters who have experienced similar.
---------- Post added at 09:02 PM ---------- Previous post was at 08:03 PM ----------
And just for the record on this thread, as suggested, I restored my backups using the TWRP command line via adb (i.e. adb shell twrp ..... ) since the screen was unresponsive. Worked, except for a couple of partitions (vendor failed with a very nondescript error message of extractTarFork() process ended with ERROR: 255 ). Retrospectively would've probably been better not to use the SD card to keep the backup on, I think using the command line to back up directly on to your PC is arguably a nicer way of doing things. But didn't matter, that got everything back to a state where the screen started working properly in recovery mode and the Huawei recovery started working again as well, so I just decided to take everything back to the original state and start completely afresh.
Hello
I wanted to go back to full stock and erase apps and files (I'm selling my Mi Mix).
I was running MIUI 8 Global Rom rooted.
I was in twrp (by Mr Raines). I wiped data, system/cache and flashed miui stock rom, and just after, without boot the rom, I did a format data (to erase everything).
I booted, but it freeze at setup (it's random, it cans freeze on "select your region" as it cans freeze on "Connect to wifi")
it freezes for around 10 seconds, then it reboots.
Again and again...
I have tried to flash twrp, but it stuck on boot screen for around 10 sec and reboot.
I have flashed the fastboot rom with MiFlash but still freeze at setup !
I really don't know what can i do now
Anybody have an idea to fix this?
Thank you
Hi again,
I managed to get it booting (by setup it bit by bit between it freeze)
I'm now able to access to the homescreen but it still freeze after few seconds and reboots.
TWRP now works but i can't transfer files to the phone. Adb sideload works, so i have tried to flash differents rom (RR, LineageOS) but they both freeze when booting (I have the boot animation, but it freeze after arround 20 sec...)
Wahoux said:
Hi again,
I managed to get it booting (by setup it bit by bit between it freeze)
I'm now able to access to the homescreen but it still freeze after few seconds and reboots.
TWRP no works but i can't transfer files to the phone. Adb sideload works, so i have tried to flash differents rom (RR, LineageOS) but they both freeze when booting (I have the boot animation, but it freeze after arround 20 sec...)
Click to expand...
Click to collapse
What does TWRP no works mean, should it be "now works" or "not working" did you format after installing TWRP? Read through the guide's again before attempting anything. MTP should work for transferring files, as in
mtp-connect --sendfile "insert file"
I see just read first post again, did you factory reset as well?
---------- Post added at 02:49 PM ---------- Previous post was at 02:25 PM ----------
You can try this if you are brave, worked for this guy which strangely enough I posted the answer under a different name.:laugh:
https://forum.xda-developers.com/mi-mix/help/constant-unfortunately-app-stopped-t3662376
james1089 said:
What does TWRP no works mean, should it be "now works" or "not working" did you format after installing TWRP? Read through the guide's again before attempting anything. MTP should work for transferring files, as in
mtp-connect --sendfile "insert file"
I see just read first post again, did you factory reset as well?
---------- Post added at 02:49 PM ---------- Previous post was at 02:25 PM ----------
You can try this if you are brave, worked for this guy which strangely enough I posted the answer under a different name.:laugh:
https://forum.xda-developers.com/mi-mix/help/constant-unfortunately-app-stopped-t3662376
Click to expand...
Click to collapse
Thank you a lot for your help, I will try this
EDIT:
I did not worked
I will flash fastboot rom and lock bootloader, and contact seller for a repair
Thanks anyway