Flashed wrong recovery.img - bootloop - Android Q&A, Help & Troubleshooting

Hello!
I have a general problem right now.
I flashed a wrong recovery.img and now my tablet is stuck in a bootloop. :crying:
I cant boot it into recovery and my pc is not recognizing it.
In device manager its visible only one second calling it unknown device.
I can not reach it with adb.
I was previously stuck in fastboot mode, because it wasnt possible to find the right fastboot interface driver. After the battery ran dry it rebooted normalyl. Hope this will be the case again.
But what if not? :crying:
Its an Allwinner a33 cheap china tablet. It will be very hard to find the correct firmware. I think, in the best case i find a very similar firmware, but want to avoid this step.
What could i try?

Related

Jiayu S3 Bricked MTK6752?

Hello guys. I need your help. I think i somehow soft bricked my dad's s3 3gb ram version.
What i have done is flashing a TWRP img. Twrp was just fine. After that i wiped and installed a rom. I think the zip was broken or something because after the processes is done twrp said there is no OS (operation system). I clicked on reboot anyway by mistake i guess...
And at this point my phone only restarts itself. I can get in FASTBOOT mode. I have the drivers and all but i dont know what can i do with the fastboot mode.. But fastboot seems stable. The phone is not restarting when it is on fasboot mode. Yet as i say again. Is there ANYTHING i can do with fastboot commands? i tried to flash a recovery twrp img it said recovery partition doesnt support flashing..
When i try to boot in recovery the phone seems to start booting to recovery but after a while it restarts itself as it does always...
I tried SP flash tool mode too. My driver is fine, i can see preloader driver on my device manager but as always phone restarts itself to boot in normal mode... If only i can stop the phone from restarting.. I have twrp backup... Or i can flash stock rom...
Please help... Any reply will be appreciated.
I mentioned my problem on the main topic of jiayu s3 but since there is so little user attention there i wanted to open a thread here as well.. Sorry if its out of rule.

Bootloader problem

Maybe I'm just stupid, but I have a weird problem.
So: I was at new bootloader and I wanted to install an old backup I made with old bootloader. So I searched on XDA for an instruction to install the old bootloader. I found this http://forum.xda-developers.com/oneplus-x/general/2-2-x-lollipop-bootloader-download-t3479948 and I flashed the second zip. I installed my old backup and there was just the oneplus Logo, without the powered by android text. I tried to boot into recovery and flash my newest OOS zip. - Buuut there was just the Oneplus Logo too. So I tried to manually boot into recovery with fastboot - buuut fastboot did not recognize it (I cant even boot into fastboot mode on phone). So I thought that I have maybe hardbricked it and I did the hardbricked guide - buuut my phone was not even recognized as the Qualcomm xxx or so. It was just nothing (and yes I checked my USB connection). So I have no idea what I have to do now. Thanks for your help and sorry for my bad english.
IchBinNoob said:
Maybe I'm just stupid, but I have a weird problem.
So: I was at new bootloader and I wanted to install an old backup I made with old bootloader. So I searched on XDA for an instruction to install the old bootloader. I found this http://forum.xda-developers.com/oneplus-x/general/2-2-x-lollipop-bootloader-download-t3479948 and I flashed the second zip. I installed my old backup and there was just the oneplus Logo, without the powered by android text. I tried to boot into recovery and flash my newest OOS zip. - Buuut there was just the Oneplus Logo too. So I tried to manually boot into recovery with fastboot - buuut fastboot did not recognize it (I cant even boot into fastboot mode on phone). So I thought that I have maybe hardbricked it and I did the hardbricked guide - buuut my phone was not even recognized as the Qualcomm xxx or so. It was just nothing (and yes I checked my USB connection). So I have no idea what I have to do now. Thanks for your help and sorry for my bad english.
Click to expand...
Click to collapse
If it's not recognized, search and ask in mega unbrick guide thread. U may find your answer there.

(Hard?) Brick Alcatel One touch pop s3 5050x need help

Firstable, i'm new to this forum so feel free to move my topic to the appropriate thread.
Hi, I need some help. I was given a bricked phone that I would like to fix.
phone: alcatel one touch pop S3 5050x
-Infinite boot loop when powered on
-it does not start with power button , only with the usb plugged in
-i have access to fastboot mode but not adb or recovery (i think USB debugging is disabled)
-when i try to flash CWM or use " fastboot boot recovery.img" i get weird white lines, like a lcd issue but the lcd seems fine, then it starts boot looping again and again
-i cannot find any stock rom in order to get clean boot.img, recovery.img and system.img and flash them
-i only found a TWRP backup but i cannot access any recovery mode or boot on it via fastboot
-converting TWRP backup files (.ext4.win) in .IMG files may help me
-Mobile upgrade won't detect the phone so it cannot download the appropriate ROM
-there is only a few files related to this phone, that's why it's so difficult to solve this.
I really need your help, i think every android brick/ bootloop is a challenge and i want to achieve it. :fingers-crossed:
English isn't my native language, i apologize for language mistakes.

How can I flash an .img file if my device is bricked?

Hello there. I have an Elephone P9000 Lite, which required a re-flash. Fair enough. After I formatted everything then flashed the stock ROM... I tried booting it up, but the boot animation won't show up, instead, it's all just a black screen. It went on like that for 10 minutes, before I decided to stop trying. It got bricked. Now, I decided to try and flash CM13 (I found a ROM on this forum), but I can't flash it using SP Flash Tool (what I used to flash stock) because it's an .img file, so it doesn't have a scatter. I came to the conclusion that I can use:
a) Recovery, which I can't access due to the device being bricked
or
b) ADB, which requires USB debugging to be enabled, but I can't enable it due to my device being bricked.
Can anyone help me?
(I have quite some experience with flashing and stuff, but I have no idea how to flash .img using a PC without having to access the phone's OS)

[Bootloop] Orange State - your device has been unlocked and can't be trusted

Hi I followed a guide in order to root my phone Mediatek Ulefone armor x2.
Code:
fastboot flash recovery [filename.img]
Code:
fastboot boot recovery [filename.img]
Code:
fastboot reboot
But now it is stuck in a bootloop saying: Android Orange State Your device has been unlocked and can't be trusted.
I can't force shutdown the device and also I can't restart in recovery mode with VolumeUP + PowerButton because it's restart in bootloop.
Also I've tried to plug in USB on a PC but adb don't recognize my device.
How can I do?
did anything work as i have the same problem please reply
Your best bet may be to reflash the stock OS. What's your device model, as well as the steps you used to unlock your bootloader? I may be able to help fix the problem
I have the same problem too. My device is a tablet. Brand CHUWI Hi9 Plus. Can someone help me?
LOLLO.EXE? said:
I have the same problem too. My device is a tablet. Brand CHUWI Hi9 Plus. Can someone help me?
Click to expand...
Click to collapse
do you fixed this problem?

Categories

Resources