Hello,
I have an a8-50f that I was attempting to flash with a new ROM because I had the wifi issue that this particular model seems to have (connection basically dropping a minute or so after connecting to wifi). I flashed a TWRP which was supposed to be for my model. The guy on the forum post in which I found the link said it worked on his a8-50f. However, when I tried to boot the device after flashing TWRP it kept failing to mount "/data". After attempting a couple things to fix it I (stupidly) lost bootloader access via adb, when I tried to wipe the drive with China Recovery.
So now it's hanging at the Lenovo boot screen. I can still access China Recovery but it doesn't seem like I can do anything with that. Does anyone have any suggestions on how to fix the system or recovery partitions from this state? Maybe how to revert the TWRP flash. I have what should be the stock system and recovery images if someone knows a way to attempt a flash without adb access.
Thanks a lot for any help you guys can provide.
*Can't post images because I'm a new account. The TWRP error screen is at /ycD6B0e on imgur.
I know it is late but try Mtkclient. https://GitHub.com/bkerler/mtkclient
After building Mtkclient start the GUI and plug the tablet in from an off state.
Hope this works.
Related
So I had been attempting to encrypt my phone for 2 days and finally today I did something and it started encryption. I had rooted the phone and had TWRP on it.
The encryption finished and it rebooted and now its stuck with the screen on the 1 logo. i can turn it off and go to the bootloader and TWRP but no matter what i do it won't let me flash anything. in TWRP I tried formatting the drive but that didn't do anything either, it keeps giving the error "Unable to mount drive"
I was trying to find an Odin type package for it but no go yet. Even LG had a flashing tool. Any ideas?
You can download the fastboot images from the official cyanogen site:
https://cyngn.com/products/oneplusone/
Transmitted via Bacon
Yes, i did have the fastboot images but it wasn't letting me flash them.
Ok, so I think I wiped out the OS while wiping the phone earlier and that's why it wasn't going anywhere after the 1 logo.
What I now did was pushed down the Pacman ROM zip via TWRP to the local drive and flashed it and its booting now. I should be able to get the rest going.
heres how i handled that exact situation and got encryption working correctly on 11S
https://forums.oneplus.net/threads/fix-fixing-encryption-and-keeping-wireless.133304/
WIFI issue after encrption
Im having issues after encrypting.
I have twrp and rooted my phone. today i encrypted my device. No issues. After password first time device dint do anything i thought its hanged or something.
powered off and started again . second time phone started without issues after decryption password. But to my surprise phone for factory reset.
But my major issue now is. Im not able to turn on wifi. Its is disabled. Can tell me what to do.
Shall i reset in TWRP ?
Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!
Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.
Cmon guys! I don't want to JTAG it yet.
HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Same thing happened to me!
Basidialfiddle said:
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Click to expand...
Click to collapse
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
gaurav.kar said:
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
Click to expand...
Click to collapse
Hi, I found the solution time ago, sorry for answering to late, hope I can still be helpful.
Well, what I did is, I booted into TWRP, then I did a total format to the storage, after that I did something kind of crazy, I switched my storage format to anotherone and then I turned it back to how it was before (example: I was on fat32, I switched to exFAT and then I switched again to fat32) after doing that I tried to flash LinageOS and it allowed me, it booted and now my friend has Android Oreo on his Moto G1
Hope it works for you mate, those situations are very frustrating, good luck
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?
My phone is stuck on fastboot mode or twrp, it cannot load its system and when i try to flash anything it gives me a bunch of errors. Before i made the twrp install i was running ui 2.0 from Realme My phone is a Realme C15 qualcomm edition, ive been stuck days now and i cant do anything, it seems like theres a problem with twrp.... System_root unmounted, vendor
ESD444 said:
My phone is stuck on fastboot mode or twrp, it cannot load its system and when i try to flash anything it gives me a bunch of errors. Before i made the twrp install i was running ui 2.0 from Realme My phone is a Realme C15 qualcomm edition, ive been stuck days now and i cant do anything, it seems like theres a problem with twrp.... System_root unmounted, vendor
Click to expand...
Click to collapse
Some "bunch" of errors can tell you something about the issue, instead you should mention some of them or upload some screenshot to get a better clue.
SubwayChamp said:
Some "bunch" of errors can tell you something about the issue, instead you should mention some of them or upload some screenshot to get a better clue.
Click to expand...
Click to collapse
I have error 7 on flashing any ROM, failed to mount system_root, vendor, E:unable to open /system_root/system/apex, e: unable to load apex images from /system_root/system/apex, failed to mount system root
Now i have logs can anyone help take a look?
I attached 2 log files
I have bricked my device two times already and almost bricked it the third time. I was saved by a ram disk stockboot.img file created by magisk. I cannot seem to install TWRP properly. All I can achieve is to flash TWRP into recovery and then boot into recovery it manages to boot up into TWRP, but the problem here is it is only once. When I reboot the system it then goes back to stock recovery. This is when I got the idea that since I could boot TWRP once why not go into it and then flash magisk. This is how after I flash magisk my device bricked. I bricked my device twice like this. I had to go to a realme service centre to get my device reflashed they were very helpful. I wouldn't want to brick my device a 3rd time, hence why I'm asking for help. Please try and help this Noobie, I am using UI 2.0 version c.09 I don't know what I'm doing wrong here because I am following all the instructions are available on the internet. It only seems to bring me to brick my device. Please anyone give some help. EDMUND SONG from Malaysia. [email protected]
ESD444 said:
I have bricked my device two times already and almost bricked it the third time. I was saved by a ram disk stockboot.img file created by magisk. I cannot seem to install TWRP properly. All I can achieve is to flash TWRP into recovery and then boot into recovery it manages to boot up into TWRP, but the problem here is it is only once. When I reboot the system it then goes back to stock recovery. This is when I got the idea that since I could boot TWRP once why not go into it and then flash magisk. This is how after I flash magisk my device bricked. I bricked my device twice like this. I had to go to a realme service centre to get my device reflashed they were very helpful. I wouldn't want to brick my device a 3rd time, hence why I'm asking for help. Please try and help this Noobie, I am using UI 2.0 version c.09 I don't know what I'm doing wrong here because I am following all the instructions are available on the internet. It only seems to bring me to brick my device. Please anyone give some help. EDMUND SONG from Malaysia. [email protected]
Click to expand...
Click to collapse
Sorry, I didn't receive any mention from your post.
The worst you can try to do is attempting to mod it, root it, in this unstable stage; you have to first recover your device to a functional state before to try anything else.
The error seems to be linked to the super partition, TWRP not getting access to, and it won't boot this way.
Extract the super image from your stock ROM and flash it through TWRP, then format data, and try to boot.
SubwayChamp said:
Sorry, I didn't receive any mention from your post.
The worst you can try to do is attempting to mod it, root it, in this unstable stage; you have to first recover your device to a functional state before to try anything else.
The error seems to be linked to the super partition, TWRP not getting access to, and it won't boot this way.
Extract the super image from your stock ROM and flash it through TWRP, then format data, and try to boot.
Click to expand...
Click to collapse
Ive got it running again...
i get same here, i tried downgrade my rmx2195 from a11 to a10 but when i boot up, my device just stuck to fastboot mode any help?
You have to find the proper way of downgrading from A11 to A10. Read the Realme forums it helps from there you can find the proper files...
ESD444 said:
You have to find the proper way of downgrading from A11 to A10. Read the Realme forums it helps from there you can find the proper files...
Click to expand...
Click to collapse
There no clue for my problem in realme forum, and i try go to my phone community and ask for help, and now i have the answer, the problem is my device just encrypt so i tried to format userdata, and my phone boot up to A10.