Hi, I assume there are some posts about this thing already but I've already read some and I'm still stuck >.<
So- I had TWRP 2.8.6.0 and Exodus ROM, was going to wipe data,dalvik etc in order to flash a different ROM, but by accident i wiped internal storage.
So I went into fastboot mode, connected the device to my PC (already got adb in my pc). did <fastboot oem unlock> ,pushed a ROM and Gapps, and flashed a twrp (using fastboot command to flash recovery.img).
then I used <fastboot reboot recovery>, and the phone stays @ fastboot mode, and i get this-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried manually booting into recovery and I get stuck at the 'ak kernel' screen right after booting my devices ( had AK Kernel before all this happend).
could anyone please guide me through this mess I've made?
Lidor167 said:
Hi, I assume there are some posts about this thing already but I've already read some and I'm still stuck >.<
So- I had TWRP 2.8.6.0 and Exodus ROM, was going to wipe data,dalvik etc in order to flash a different ROM, but by accident i wiped internal storage.
So I went into fastboot mode, connected the device to my PC (already got adb in my pc). did <fastboot oem unlock> ,pushed a ROM and Gapps, and flashed a twrp (using fastboot command to flash recovery.img).
then I used <fastboot reboot recovery>, and the phone stays @ fastboot mode, and i get this-
I tried manually booting into recovery and I get stuck at the 'ak kernel' screen right after booting my devices ( had AK Kernel before all this happend).
could anyone please guide me through this mess I've made?
Click to expand...
Click to collapse
If you were rooted already why did you unlock your phone again? why did you flash a recovery again. If you were rooted and wiped everything how did you accomplish that? Through recovery I assume correct? Sorry just trying to fully understand what you are doing.
If you were already rooted it should be boot into recovery then push a rom and gapps over then flash
Are you holding the right keys down to boot into recovery vol - and Power
Hope you made a backup. All you need to do is flash a ROM, though if you wiped internal you may as well return to stock.
Sent from my SGH-M919 using Tapatalk
Related
Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.
Lidor167 said:
Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.
Click to expand...
Click to collapse
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.
playya said:
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.
Click to expand...
Click to collapse
the recovery is named recovery.img
I tried a toolkit but its too bulky for me
Lidor167 said:
the recovery is named recovery.img
I tried a toolkit but its too bulky for me
Click to expand...
Click to collapse
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?
playya said:
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?
Click to expand...
Click to collapse
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit
Lidor167 said:
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit
Click to expand...
Click to collapse
Wugs makes a descent toolkit.. Did you get it fixed
playya said:
Wugs makes a descent toolkit.. Did you get it fixed
Click to expand...
Click to collapse
yeah, appreantly the file name was - recovery.img.img but it didn't show, I had it checked and now it's all good, thanks
I don't know why. I used erecovery with FirmwareFinder many time and it work all times.
But 1 day before, I unlocked bootloader, flash patched ramdisk.img (Magisk), and then reboot again. But then it meet bootloop, bootloader relocked, FRP lock. But this time, when I use Firmware Finder to recover, it cannot work, erecovery failed when getting package. I checked all step.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My mate 9 is briked in i install the last firmware oreo b369... Firmware finder
Please help me! 41$ for 5 credits FunkeyHuawei is too much for me. Could I buy 1 credit to flash firmware?
Are you still having issues, if so, have you been able to unlock your bootloader and flash a custom recovery? If you have I think I may be able to help you
@shae23: Thanks. If I have been able to unlock bootloader, I don't need to creat this thread. I had to bring it to a service shop (Viet Nam), it cost about 6.5$ US to reflash firmware.
someone know what to do ?!!
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP
Update: I can not access the recovery anymore. its just stuck at stock recovery with EMUI 0%
Tried to flash stock and custom recovery, but no luck
Update 2: I somehow managed to get into recovery. recovery is good now.
BUT still no luck with booting, I feel it's something stupid that I missed
Did you try this way?
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
didn't work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Long wait over! Finally working TWRP for Micromax Infinity N12
- Full Treble Support
-Capability to flash all GSI
-ADB fully working
- Latest version 3.1.1
- MTP
- Encryption ( can be fixed but causes problems like battery drain)
-This image didn't boot for some people. This is due to the some vendor patches from an OTA update. To install TWRP just install the stock firmware and follow the steps below. (just don't allow the phone to install the OTA update or else the vendor patches will come back)
- Install stock rom before flashing TWRP.
- Enable OEM Unlocking
- Type the following commands
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot
recovery.img
drive.google.com
https://androidfilehost.com/?fid=8889791610682881821 stock firmware
@lopestom for the base TWRP that I ported
Works well, just encryption needs to be done
Good job. There has been no development for this device. Thanks to you l could install Android 10 gsi!
Thanks for your reply
If you like the recovery that I ported please click the thanks button, this is my first post
SOLVED
JOSHUA....... said:
Good job. There has been no development for this device. Thanks to you l could install Android 10 gsi!
Click to expand...
Click to collapse
Encryption ploblem is solved please check out
After flashing twrp, phone not booting into twrp. What will be the reason?
Fixed
Voolyo said:
After flashing twrp, phone not booting into twrp. What will be the reason?
Fixed
Click to expand...
Click to collapse
Sorry for the late reply.
Which way did you use to flash twrp? Sp flash tool or fastboot mode? If you used fastboot use it in the exact same way
Fastboot oem unlock
Fastboot flash recovery recovery.img
Fastboot reboot
After that don't let the phone reboot. Immidialy after executing the command fastboot reboot, press the power and volume up, and select recovery.
If still not successful, first flash the stock recovery and then the twrp
Edit : oh sorry I didn't see that you fixed it
Tab E said:
Sorry for the late reply.
Which way did you use to flash twrp? Sp flash tool or fastboot mode? If you used fastboot use it in the exact same way
Fastboot oem unlock
Fastboot flash recovery recovery.img
Fastboot reboot
After that don't let the phone reboot. Immidialy after executing the command fastboot reboot, press the power and volume up, and select recovery.
If still not successful, first flash the stock recovery and then the twrp
Edit : oh sorry I didn't see that you fixed it
Click to expand...
Click to collapse
Thanks for the reply .
so i was trying to install TWRP so i can install custom ROM, and accidentaly wiped the data, phone wont boot only would tell phone has destroyed, still got access to fastboot , no luck for recovery (even before it got bricked, power up + power btn wont get me into recovery, it just would boot me into the AndroidOne)
tried flashing with MiFlash tool, no luck only getting error while erasing boot_a ( i suspect that while i accidentally deleted the whole data , it also almost deleted all of the partition), i've been looking around google for days now, all of em would just flash easily,even on EDL it still doesnt work
note:
before it got bricked, i got ADB access, and unlock bootloader option ticked
would like to know any suggestion what i should try , thanks
Luqman Fuad said:
so i was trying to install TWRP so i can install custom ROM, and accidentaly wiped the data, phone wont boot only would tell phone has destroyed, still got access to fastboot , no luck for recovery (even before it got bricked, power up + power btn wont get me into recovery, it just would boot me into the AndroidOne)
tried flashing with MiFlash tool, no luck only getting error while erasing boot_a ( i suspect that while i accidentally deleted the whole data , it also almost deleted all of the partition), i've been looking around google for days now, all of em would just flash easily,even on EDL it still doesnt work
note:
before it got bricked, i got ADB access, and unlock bootloader option ticked
would like to know any suggestion what i should try , thanks
Click to expand...
Click to collapse
error on Fastboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
error on EDL:
Hello all
need some help with the mentioned phone that is stuck on the Asus logo when powering up
i have tried to go into the recovery / reset mode but for some unknown reason all i can seem to get is CSC fastboot mode long press power key to shutdown and nothing else even using up and down volume nothig
i tried using tools like minimul ADB as well as fastboot platform tools now with ADB minimul phone did respond to it once but after nothing else..... the fastboot platform tools does respond and when using the command fastboot devices it will show up what appears to be a serial number another command fastboot recovery i believe will make the phone shutdown and reboot back into fastboot mode this time with what apeears to be a barcode on the right side of the screen
now i have a sneaky feeling that the phone has somehow corrupted the boot partition or where ever the boot files are located preventing me to boot phone or even get into recovery for a factory reset
now as mentioned above my phone is communicating with the computer so tho i am assuming only the platform tools will work with fastboot commands but adb wont work properly due to debugging mode not enabled
does anyone have any solutions and detailed instructions on how to fix the problem without firmware flashing
i will happily flash the firmware as a last resort but would need some advice on software to do this as i am used to MTK chipsets and using SP flashtools but this model phone isnt MTK
i tried
fastboot reboot recovery
but don't work
any help would be appreciated
many thanks
fastboot reboot recovery is not a valid command, so it's same like fastboot reboot
not sure what is the problem with that phone. maybe it's just end of life/emmc wear-out.
you can try fastboot continue that would boot into android ignoring volume key in case button stucks/short-circuited/wet.
if that doesn't help you can post the output of
Code:
fastboot oem device-info
fastboot flashing get_unlock_ability
flashing is possible from EDL mode, but that won't fix hardware issues:
Bootloop issue and can't go to recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit: please don't post foreign text from other threads persuade you are firm with SP Flash Tool (when you're actually not)