Guys, in need of desperate help here!
I've heard my friends joking that girls are not good with tech so I decided to prove them wrong by flashing a custom ROM on my newly acquired Vernee Apollo phone. Well, that ended badly - I succeeded rooting it and installing SuperSU, but I bricked it when I tried flashing a ROM so now when I turn it on it stays on the Vernee logo.
I suppose I have to open TWRP recovery and reset my phone with the backup I created earlier but I can't access it - I can only access Recovery Mode and FastBoot Mode
In FastBoot mode I try to connect the phone to my PC and get to TWRP but adb doesn't find my device anymore...
And In Recovery mode, when I try to flash the ROM, it using 'Apply update from SD card' it says 'Opening update package...' and right after that 'Installation aborted' (and my battery is almost full).
Any help is appreciated! <3
Related
I'm using a lenovo s820, rooted, running stock rom and jb 4.2.1
I couldn't find any recovery like cwm or twrp for my phone and I ended up downloading a recovery that said it was a version of cwm for my phone from this app called mobileuncle mtk tools
The app flashed the recovery onto my phone and rebooted into recovery except that it didn't boot into recovery
Now it is stuck in a boot loop where it only shows the lenovo logo but does not boot
I've tried booting into recovery by holding "vol up+vol down+power" but it does the same thing
I tried booting into factory mode but it is in chinese and I cannot understand anything in it
I have a backup of my rom before flashing the recovery but it is stuck in the boot loop even after restoring the backup
I've also searched a lot and can't find a solution to my problem!
I've seen some solutions saying I should flash stock rom using flash tools but there's a big problem here. Flash Tools refuses to flash the stock rom onto my phone. I tried to do it while keeping the phone in meta mode but it wasn't happening.
I've attached the image of the factory mode menu
Please help asap! I can't use my phone at all and I'm panicking and I don't know what to do!!! :crying: :crying: :crying:
Update: I managed to restore clockworkmod recovery on my phone and I tried to restore the stock os from it but it says installation aborted and refuses to install the os :/
Look here:
http://forum.xda-developers.com/showthread.php?t=2576898
My Lenovo A316i does not turn on anymore but can still be recognized by the computer. At first, my phone can be powered on but restarts at the logo. I made it worked using SP Flash Tool and I installed TWRP. The problem occured after I install an updated.zip folder through TWRP without Wiping. The phone at this stage was stocked at the logo. Then I tried the "Format all & Download" option in the SP Flash Tool. Now it does not turn on, but can still be recognized by the computer.
I already followed the steps from these videos
https://www.youtube.com/watch?v=A3TmXtOA0IA
https://www.youtube.com/watch?v=hKYH7gkvrvY
Try to flash with stock rom dude
I already did but it's still not working.
Are u able to go to TWRP recovery mode
No because it's not turning on anymore.
Try to use button combination for your phone model
hello,
i tried to install custom rom on bobarry k10se tablet (chinese tablet) has mediatake processor.
1) I wrongly did boot recovery with twrp image file with flashify mobile apk-- its showing bootloop only
2) then at recovery mode I tried to do wipe data and then wipe partion then I tried to install rom from sdcard but it shows - installation aborted.
3) at last i did back up & restore in recovery mode.. god.. its stuck to the flashing green robot screen and wont do anything else.
Please help me what should I do now, after starting the tablet it shows green flashing robot with written "installing system update" and nothing happnes.
I know I have done lots of mistake and tried to install custom RR 5.8.0 which failed. pls help this frnd.
i tried to flash with sp flash tool with other phones stock rom having same processor mt6580. (format all + download)
first it was installed successfully but tablet is not opening.
so again tried download only but it shows as brom error s_ft_enable_dram_fail (0xfc0).
please help me friends
i think its hard bricked now. its like switched off. if i connect to the pc via usb, there is only connecting-disconnecting sound.. nothing else happens.
i used sp flash tool with similar kind of firmware, the result shows- s_ft_unable_dram_fail (4032).
pls help me
Hi !
I see that you posted again here https://forum.xda-developers.com/an...rd-bricked-t3548246/post70826170#post70826170
Let`s keep everything in one place
Good luck !
thread closed
Hello, I have a GT-S7560m (Galaxy Trend or Ace II)
Just tried to install the custom recovery too much times, I tried with TWRP official app and didn't worked, tried with ADB, but fastboot won't detect my phone on download mode, and finally tried with TWRP Manager App (here the brick), the APP said I already instaled a custom recovery (but I know not, this is my first time at rom flashing), and then the app asked me to reboot the phone, after reboot, the phone won't boot anymore!
Some specs are there the phone don't show up anything on the screen (like logo or information), don't vibrate, don't boot on recovery or download mode, BUT, any PC recognize it as Serial USB device (COM3, COM5, or COM6), but adb don't find anything!
I don't know whatever happened to my phone, I didn't tried to install custom rom, I was just taking a look at the custom recovery, that I don't installed too
And yeah, my phone was rooted, and I downloaded TWRP from official site, my device is supported, I found out twrp kyleve 3.0.0.0
What to do? It's not a Hard-Brick, I know it :crying:
VitorMac10 said:
Hello, I have a GT-S7560m (Galaxy Trend or Ace II)
Just tried to install the custom recovery too much times, I tried with TWRP official app and didn't worked, tried with ADB, but fastboot won't detect my phone on download mode, and finally tried with TWRP Manager App (here the brick), the APP said I already instaled a custom recovery (but I know not, this is my first time at rom flashing), and then the app asked me to reboot the phone, after reboot, the phone won't boot anymore!
Some specs are there the phone don't show up anything on the screen (like logo or information), don't vibrate, don't boot on recovery or download mode, BUT, any PC recognize it as Serial USB device (COM3, COM5, or COM6), but adb don't find anything!
I don't know whatever happened to my phone, I didn't tried to install custom rom, I was just taking a look at the custom recovery, that I don't installed too
And yeah, my phone was rooted, and I downloaded TWRP from official site, my device is supported, I found out twrp kyleve 3.0.0.0
What to do? It's not a Hard-Brick, I know it :crying:
Click to expand...
Click to collapse
Hello and welcome to xda-assist,
Please get further help on general help section...
http://forum.xda-developers.com/android/help
Good luck
Hi guys, i need your help!
i will try to explain the situation at my best.
A couple of days ago i decided to go back from a custom ROM to the Stock one via TWRP flash and i ended up with a soft brick, later i managed to flash the stock rom with SP Flash tool.
Yesterday i tried to get ROOT access on the fresh installed stock rom and considering that i wasn't able to get ADB and Fastboot to work properly on my pc (at the time) i used King Root, after that i tried to install TWRP through the official app, the result was not successful (the problem was the locked bootloader) and i found myself without recovery (neither TWRP or Stock).
Here comes the last part (the tricky one)
after all this mess I managed to get ADB and Fastboot to work and i obviously tried to unlock the bootloader, unfortunatly i hit "boot to recovery" and now i'm stuck with a boot loop with no recovery.
if i try to get to fastboot with Vol down+Power the phone shows the LeEco Logo and then the screen shuts down.
Sp Flash tools doesn't work either.
Any possible solution?
The thing u got wrong is that... U should have flashed twrp on either eui 5.8.17s or 5.8.19s...
Don't flash it on 14s or lower eui version ... It might get stuck on bootloop