Long Version
Okay, here's quick debriefing. Yesterday evening I attempted to flash the (Beta) UberSlimLP rom. I'm not new to flashing roms, I went through the normal routine. Downloaded the rom, gapps, did an application backup, did a nandroid backup with TWRP, did a full wipe (System, data, dalvik, and cache), and flashed the rom and gapps. Also flashed the KK bootstack because the rom thread said that the KK bootstack was required. After booting, right off the bat there were baseband issues. So I said, oh well and restored the backup.
The thing is, after restoring my phone, it got trippy. It would respond to touches about 5 seconds after i tapped the screen. And if the screen would time out, it wouldn't respond at all after that. Not to mention if I dragged down the notification bar the system would crash and the phone would freeze up. Don't worry though, it gets worse. For some strange reason I lost TWRP and in several vain attempts to get it back I only made my phone worse.
===========================================================================================================================================
Short Version
Every time I boot up my phone it goes straight to fastboot mode and every time I send a fastboot command it fails so I can't really install TWRP,CWM, or any other recovery.img for that matter. Any help? :crying:
My advise (maybe not the best) reinstall stock rom with kdz.. Flashing bootstack maybe was the problem.. If you were in kitkat you didnt needed to flash it..
Enviado do meu LG-D405n através de Tapatalk
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
http://forum.xda-developers.com/showthread.php?t=2803479
Enviado do meu LG-D405n através de Tapatalk
Something similar happened to me today. Only I bricked it myself. Try booting into factory reset (powerbtn + voldown, hold until lg logo appears, then let go and put your fingers on the powerbtn+voldown again). If it gets you there, do the factory reset but don't reboot when the screen goes black, try attaching it to a PC. I'm at the moment on Linux, trying to find the boot partition so I could rewrite it.
Thanks but,
Warimation said:
My advise (maybe not the best) reinstall stock rom with kdz.. Flashing bootstack maybe was the problem.. If you were in kitkat you didnt needed to flash it..
Enviado do meu LG-D405n através de Tapatalk
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
http://forum.xda-developers.com/showthread.php?t=2803479
Enviado do meu LG-D405n através de Tapatalk
Click to expand...
Click to collapse
The last 5 times I tried to flash the kdz it failed.
here you go.
da0n3e said:
Something similar happened to me today. Only I bricked it myself. Try booting into factory reset (powerbtn + voldown, hold until lg logo appears, then let go and put your fingers on the powerbtn+voldown again). If it gets you there, do the factory reset but don't reboot when the screen goes black, try attaching it to a PC. I'm at the moment on Linux, trying to find the boot partition so I could rewrite it.
Click to expand...
Click to collapse
I found this in the FAQ, maybe this is what we're looking for?
All the stock partitions by shinobisoft. The only problem is that although it boots straight to fastboot, all the commands I send fail...
Related
Was installing android revolution 10.0 and when it finished it wen't back to CWM. It said something about maybe loosing root and I accidentally backed out and it tried rebooting. Now its stuck in some sort of bootloop and it tries to boot into ROM but it turns off and then trys to boot reecovery. the screen flashes CWM for a second but then it turns off again and trys to boot. I can get to Hboot and selecting recovery there makes the same thing happen.
xXxG0dzRAgexXx said:
Was installing android revolution 10.0 and when it finished it wen't back to CWM. It said something about maybe loosing root and I accidentally backed out and it tried rebooting. Now its stuck in some sort of bootloop and it tries to boot into ROM but it turns off and then trys to boot reecovery. the screen flashes CWM for a second but then it turns off again and trys to boot. I can get to Hboot and selecting recovery there makes the same thing happen.
Click to expand...
Click to collapse
Can you format data?
fastboot erace cache
skinsfanbdh said:
fastboot erace cache
Click to expand...
Click to collapse
This worked. Should I try flashing ARHD again? its the only ROM on my SD card. Or should I be able to boot in to my current ARHD ROM that I tried installing before this happened?
Also at the bottom of CWM i get can't mount /cache/recovery/command and a few other can't mount log and can't open logo. before your solution I reflashed CWM using fastboot. Don't know if thoes things will cause an issue
xXxG0dzRAgexXx said:
This worked. Should I try flashing ARHD again? its the only ROM on my SD card. Or should I be able to boot in to my current ARHD ROM that I tried installing before this happened?
Click to expand...
Click to collapse
im running ARHD 10 now i would try to reflash or maybe you got a bad download
---------- Post added at 11:20 PM ---------- Previous post was at 11:20 PM ----------
oh and its running absolutely perfect btw
skinsfanbdh said:
im running ARHD 10 now i would try to reflash or maybe you got a bad download
---------- Post added at 11:20 PM ---------- Previous post was at 11:20 PM ----------
oh and its running absolutely perfect btw
Click to expand...
Click to collapse
I was on trickdroid before. I think it had to do with me rebooting and not selecting the fix root option.
reflashed and aroma got stuckk after installing. just did adb reboot and seeing whats happening next. wish me luck. :x
Let your phone cool down before trying aroma again but mine froze at 100% twice. First time got stuck at boot animation. second time it booted but it stayed at boot animation for a while
Sent from my HTC One using xda premium
skinsfanbdh said:
Let your phone cool down before trying aroma again but mine froze at 100% twice. First time got stuck at boot animation. second time it booted but it stayed at boot animation for a while
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Well I flashed it and it got stuck at boot animation for about 20 minutes. Flashed it once more and it did what it did the first time. I noticed that aroma completely crashes before finishing and thats how it all started the first time. It goes back to recovery. So just flashed it again right now and got it to completely go through. Back to HTC One screen though. Gonna see if it boots or not.
Still at boot screen for a long time. :x
skinsfanbdh said:
fastboot erace cache
Click to expand...
Click to collapse
Hi guys, I'm pretty new to this. Can some one explain how to erase cache?
xXxG0dzRAgexXx said:
Well I flashed it and it got stuck at boot animation for about 20 minutes. Flashed it once more and it did what it did the first time. I noticed that aroma completely crashes before finishing and thats how it all started the first time. It goes back to recovery. So just flashed it again right now and got it to completely go through. Back to HTC One screen though. Gonna see if it boots or not.
Still at boot screen for a long time. :x
Click to expand...
Click to collapse
the first boot is slow ..not 20 min though, more like 3-5 min
emil.kako said:
Hi guys, I'm pretty new to this. Can some one explain how to erase cache?
Click to expand...
Click to collapse
You remember how you had to do fastboot to unlock bootloader? go to that folder where you have your adb files and what not, then you need to Shift + right click while in the white space of that folder and click "open command window here." With your device connected in the command window just type "fastboot erase cache" and that'll work.
If you never had to unlock bootloader you probably had to do this already to install a recovery.
BTW Still stuck at HTC One screen. Might try flashing trickdroid 5.6 from my computer if thats possible... And as a last resort wipe data and install if that doesn't work.
xXxG0dzRAgexXx said:
You remember how you had to do fastboot to unlock bootloader? go to that folder where you have your adb files and what not, then you need to Shift + right click while in the white space of that folder and click "open command window here." With your device connected in the command window just type "fastboot erase cache" and that'll work.
If you never had to unlock bootloader you probably had to do this already to install a recovery.
BTW Still stuck at HTC One screen. Might try flashing trickdroid 5.6 from my computer if thats possible... And as a last resort wipe data and install if that doesn't work.
Click to expand...
Click to collapse
Does anyone know how i'd be able to do this using a mac?
edit: Nvm, i got it. Trying to reflash the rom now. Thanks for the help!
Just decided to wipe SD card and try ARHD again. Man I should have never tried to flash a 4.2.2 ROM yet.
No idea how to do it on Mac. Look up how to use fastboot on Mac
I got it to install correctly after erasing the cache. The first reboot took like 3-4 mins but it finally went through and it's working perfect now. Not sure what happened the first time
emil.kako said:
I got it to install correctly after erasing the cache. The first reboot took like 3-4 mins but it finally went through and it's working perfect now. Not sure what happened the first time
Click to expand...
Click to collapse
Lucky you. Im still trying to get this to work. I stay on boot screen for 20 minutes and for the 10th time im trying to flash ARHD but it keeps getting stuck. This is ridiculous.
finally I got it to boot up. Had to wipe my phone though for it to work. Lost a lot of stuff. :/
Stock Lolipop with root, xposed, TWRP.
I woke up and my battery had died, which was strange since I went to bed with 80%. When I juiced her up and turned it on, I can't use my phone. I keep getting messages "Unfortunately ____ has stopped" for all my processes and apps, and when I click OK it just keeps coming up and I can't do anything on my phone.
I tried to factory reset in TWRP but even though it says it is successful, it does not appear to actually wipe the data partition, although I do get an error when wiping...
The log looks like:
Wiping data without wiping data/media Done. Formatting Cache using make_ext4fs function. Updating partition details. . . E: Unable to stat 'data/data/com.amazon.mp3/app_NORMAL_ANONYMOUS/1478265899370'
Any recommendations on what to do?
I don't perfectly understand your problem but in this extreme case I will try to flash a custom Rom + gapps, try to see if all basic functions works and then re-flash stock one. Try again basic functions and after all is done re-flash xposed.
I have a XT1052 model now with custom Rom but for some week I lived with stock + xposed without problem.
Yeah I dunno what's happening.
I tried to flash a stock image via twrp and it doesn't work.
I tried to flash the stock image from motorola's site via fastboot and it's not working either. It says it's successful and that files are written, userdata deleted, etc. But when I boot up my phone it's not actually any different and it's still bugging out with all of my apps crashing.
Maybe I'll just buy a moto z play.
I have the exact same problem
Some user here tell me that the emmc chip (storage memory) of the phone just messed up, so, its dead.
I also cant install, erase or flash anything from and to the phone.
Enviado desde mi XT1563 mediante Tapatalk
Marco Lomas said:
I have the exact same problem
Some user here tell me that the emmc chip (storage memory) of the phone just messed up, so, its dead.
I also cant install, erase or flash anything from and to the phone.
Enviado desde mi XT1563 mediante Tapatalk
Click to expand...
Click to collapse
Well, if you eMMC is dead you can't do much. You need to find a new phone unfortunately or send for RMA if you can (but I don't think).
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
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Use smart swirch recovery method in help tab. The process guide you to process. Dont worry it will be ok.
Sent from my SM-N950F using Tapatalk
---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------
In more there is option of emergency software recovery, plug phone and it will help you.
Sent from my SM-N950F using Tapatalk
Try installing the last rom... one which is showing up in ur pc... remove any encryption if its there.... that should solve ur problem.....