Hello, I know simulair threads have been made. But this problem is more specific.
A friend of mine has bought, even I told him not too, the ACE-i. He was very happy with it and looked for a way to root it. He did it by applying a file with his recovery. The phone rebooted and didn't start (stuck on bootscreen). He can't get into download mode, withs sucks. However, recovery is ACEssible, so I tried (after he did) to install a custom rom. It didn't work. Then I tried to format system, but there was a mount error. I discovered that the system isn't accessible. Is there a way to fix this guy's phone?
Cheers, nathan-96
nathan-96 said:
Hello, I know simulair threads have been made. But this problem is more specific.
A friend of mine has bought, even I told him not too, the ACE-i. He was very happy with it and looked for a way to root it. He did it by applying a file with his recovery. The phone rebooted and didn't start (stuck on bootscreen). He can't get into download mode, withs sucks. However, recovery is ACEssible, so I tried (after he did) to install a custom rom. It didn't work. Then I tried to format system, but there was a mount error. I discovered that the system isn't accessible. Is there a way to fix this guy's phone?
Cheers, nathan-96
Click to expand...
Click to collapse
So, the real problem here is that you can't access Download mode, because if you could, you could reflash stock rom. I've found someone that had that problem, and solved it:
Here
There are lots of solutions there, hope they work!!
Press Thanks button if helped.
Hello everyone.
I don't know what happened but my device entered in the infamous bootloop. I tried to erase cache, partition, reinstall a rom, install a different rom and nothing.
My true problem is that last night I made a horrible mistake: I erased everything including my SD card, which contained the data for boot to recovery. Right now I can only see the SONY logo when I power up my device and nothing else.
I tried to install recovery via fastboot flash boot boot.img but I can't keep my device in fastboot. I mean, I connect my device and hold Volume Up but after a few seconds it continuous to the SONY logo and stays there forever.
Am I missing something? What can I do to reintall a recovery if I can't access my phone data?
Thank you.
How to install recovery in a phone which can't start [Solved]
I just figured it out! I installed Sony's stock rom following this guide and my phone is alive again.
bbabel said:
I just figgured out! I installed Sony's stock rom following this tutorial and my phone is alive agaoin.
Click to expand...
Click to collapse
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
kwitu said:
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
Click to expand...
Click to collapse
Thank you. I just fixed the link and now it works.
Hello people, sorry for the long post, but i hope theres sufficient information to help you help me.
So... I come here to ask for your help and opinion. I need your guidance.
History: I was using my Moto G (2nd gen) to control the Smart TV Youtube App when, suddenly, my phone freezed completely. I tried to lock/unlock the screen and to turn off but it reset by himself and i was "oh, ok, good". Well, not so good. When it turned on again it showed the Motorola blue logo screen but turned off. Then turned on again, showed the logo, turned off and stayed is this loop until the battery went dry. After recharging i tried to turn it on again, but the same thing happened. I also tried to enter Recovery and Factory Reset but, again, the same thing happened. It doesn't even shows the screwed android logo upon recovery selection.
I made some research hoping there was a way to access the internal memory, to backup everything i could, before sending it to the technical assistance (i would copy even system files if possible).
I connected via usb to my computer, tried adb, tried fastboot, nothing worked.
Reading about fastboot stuff i found this comments on a website ( lifehacker .com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225 ):
"Another thing that most guides out there seem to miss.... If you need to do something in a custom recovery ROM, you do not need to flash it. You can just directly boot it from a local image on your computer using adb. A lot less destructive.
Something like:
adb boot CMR.img"
"I don't think he means "destructive" in the sense of it harms your phone. But rather, that using one recovery does not mean you have to eliminate the previous one. Say you want to try out some feature of TWRP, but you really like Clockworkmod Recovery. This would allow you to run TWRP temporarily, while still keeping Clockworkmod as the default recovery.
Sort of like using a Live DVD to boot into Ubuntu without destroying your Windows partition."
Now my question(s) is(are): Can I do something to save some data without compromising my warranty, so I can send my phone to Assistance later?
If I can flash the ROM (and access my data), do I need to unlock and/or root the phone? Is this process reversible?
I hope you can help me, thanks.
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
Hello XDA,
I'm not sure if this is the right spot to ask about this, lemme know if it is.
Right, time to get to the problem I'm facing.
I've got an Asus ZC500TG in this year's August, rooted it the same month, and everything was working fine until last night.
After doing a basic procedure of using TWRP 2.8.7.0 to flash Infinix Hot 2 AOSP port(was working for me many times), the device decided to just boot into recovery even though i pick 'boot to system'.
The bad news don't stop there either. When I plug my phone with USB while it's powered off, instead of going into the ROM part that shows the battery symbol and charges... it goes back into recovery instead?
Also, doing the keystroke(holding power+volume up), instead of going into bootloader mode(the thing that lets you pick between recovery, fastboot and normal boot), it also boots to recovery instead.
If i boot to fastboot through TWRP, it boots into fastboot fine, but that's pretty much it. Fastboot and recovery modes is the only thing I can access.
Even though I was with the rooting community ever since I've had my first smartphone in 2012, I've never experienced such an issue where the only thing bootable is either Recovery or Fastboot using the said recovery.
Here's what I've tried so far:
-Wiping cache/dalvik cache/system/data;
-flashing a known working stock ROM;
-Trying to sideload it using TWRP's ADB sideload, seemed to check out and came back to same issue;
-Trying to flash/sideload custom ROMs I know should function properly, same issue occured;
-Flashing stock recovery back and attempt to flash stock ROM, also failed;
-tried to wipe /system, /data, /cache and /dalvik-cache using fastboot, then flashing ROM using recovery, also failed;
-looking up anything that's related to it, mostly fraud websites and/or Russian websites suggesting to do what I did already.
Has anyone ever encountered this, and is there a possible fix to this?
Thanks in advance to all your answers.
-MrRubikon
Help me zenfone go zc500tg zoovd my phone is wrong root then total dead can not live
antho111 said:
Help me zenfone go zc500tg zoovd my phone is wrong root then total dead can not live
Click to expand...
Click to collapse
I have some problem,,
,,somebody can give solution pleace,,!?