Hi guys, I really need your help!
I have a Vernee Apollo Lite and it's stuck in bootloop......
Can't enter in recovery mode (Tried flashing TWRP multiple times via fastboot with a Mac)
I'm also stuck with no OS, originally I got TWRP working and wanted to flash a custom rom (MadOS Oreo 8.1 AOSP)
but I messed up and wiped everything (the partitions).
Tried to flash it anyways but gave me Error 7 so I tried other roms but other problems occured and failed each time, I tried flashing another recovery.img file (TWRP) in recovery mode and rebooted but then it didn't load anymore so all I have right now is fastboot working.
Tried flashing a stock rom via fastboot but kept giving me "remote: partition table doesn't exist"
I wonder if I could use the flash-all command with the stock images but some are missing in the the stock rom file but probably it will still give me the same error (partition table doesn't exist)... oh and I also tried flashing custom roms with fastboot but no success.
VERY IMPORTANT TO KNOW THAT I ONLY HAVE A MAC By the way I checked each files and compatibility isn't the problem.
Thanks in advanced:good::good::good::good:
Related
Hi all, I tried to flash twrp after unlocking bootloader but the site I followed was wrong, ended up with twrp on boot partition! I've since tried to fastboot various system and boot images with no luck, keeps giving file size errors. Booted twrp from fastboot to flash lineage but that ends with error code 7?! Tried to fastboot update stock room too but same problem with file size, the system img is actually broken up into 50 odd files, I presume to avoid the file size problem, however there's no flash all script. Help!!
Hello everybody!
The last day my phone got stuck on bootloader screen. It just wouldn't boot the OS.
So I tried to fix that by flashing other rom. I have unlocked it trough MiUnlock.
Flashed in fastboot TWRP(rosy) recovery. It could boot TWRP but after a reboot, would launch MiRecovery.
After that the Android didnt start no more. After a new flash of TWRP I was able to enter recovery. I tried to flash a custom rom. After that the VOLUME UP + POWER wouldnt launch recovery no more (Also VOLUME DOWN+UP+POWER buttons, wont boot the Recovery)
Now i found an EDL mode to flash rom through XiaoMiFlash. Did it, Made the steps from tutorials. That, has changed the device to COM10 in MiFlash which let me try different official roms, and i always get the same error message: cannot receive hello packet, MiFlash is trying to reset status!
Also tried too flash a recovery img.
Tried everything i found on that, nothing worked to get those packets...
My only hope was to fastboot flash recovery TWRP or MiRecovery. And then flash new rom to fix my phone.
Tried many version of Twrp, but no success to actually flash.
I have tried removing recovery via adb and flashing another. Logs shows success but no effect on phone.
Still can't acces recovery mode on my phone.
Bootloop stuck. Shows MI logo and that its Unlocked.
Doesnt work flashing via fastboot - TWRP or MiRecovery images.
My phone is bricked for a week now. Please share a solution if you got one.
SOLVED
Good news. finally flashed chinese version through miflash tool.
had to rename some files from rom.
Flashed through BOOTLOADER.
So it's my second attempt to flash lineage os (unofficial) on my Realme XT. First time I was a little careless and bricked my device (had to go to the service center for that). Second time I took all the precautions still I'm having almost same problem, but this time its not yet bricked.
I unlocked the bootloader. It went fine.
Flashed unofficial TWRP and booted back to stock os.
When I tried booting to TWRP again I realized it was reset back to stock recovery. So I flashed it again and made backup of all the partitions (stupidly on internal storage). Booted back to system to check that backup is showing on internal storage. Again booted to TWRP and wiped everything except internal storage, flashed lineage and gapps. Wiped dalvik/cache rebooted to system. I was greeted with system partition destroyed error screen.
I flashed vbmeta.img via fastboot, the error was gone but still i was not able to boot to lineage. (I directly flashed vbmeta.img via fastboot. Didn't use the "fastboot --disable-verity --disable-verification" command.)
Now I'm having a different kind of problem.
I can boot into TWRP but I can not boot to system (lineage os). Can't go back to stock as well because the internal storage is encrypted i think (all the folders have random names). After flashing vbmeta.img (via fastboot) now I am not able to connect my phone via fastboot.
Without fastboot TWRP backup is the only option for me to get it back in a working state. If anyone reading this has stock color os with TWRP, It would be great help if you could give me a TWRP backup of system.
Also, I would ilke to know where I messed up while unlocking/flashing, so that I can avoid this in the future.
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
There is a flashable twrp stock rom.. in guides section. Flash it in twrp.
Thanks I'll try that!
naushad.016 said:
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
Click to expand...
Click to collapse
How you managed to get fastboot ?
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
You cannot flash the StockRomXYZ.ozip file directly via TWRP or OrangeFox recovery but if you want to flash COLOR OS then use this link - https://forum.xda-developers.com/realme-xt/how-to/official-ota-update-rmx1921ex11-11-26-t3993041 to download and flash directly otherwise convert the .ozip file into .zip file before flashing. Try the steps mentioned in the link to convert - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277 . After conversion, copy the .zip into storage and always use the Clean Flash method to flash the firmware.
Hope you got it.
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
Hi!
I was trying to install new ROM via OrangeFox (R10.0) but it always give me the error 7. Trying to solve this now my phone only gets to fastboot via EDL and when trying to flash stock ROM it got stuck endless at flash modem.
Things i did (Using OrangeFOX R10.0 and Flash Tools 2019.12.06):
-Install ROM directly, as i always do. Gives me the error 7 saying "if it is the correct device".
-Install latest firmware then ROM. The firmware install says that its already find same version on device and install again, but trying to install ROM after still give error 7.
-Install firmware, wipe all, reboot, rom. Still error 7
-Tried to go back to stock but from recovery ROM gives error 7 and from fastboot gives me the Mismatching device.
-Tried to format first data partition (via OragenFox), but still gives me the same error.
-Tried to fix the "Mismatching device" on fastboot flash doing this www.youtube.com/watch?v=_osMF9EubhI. When trying to flash first gives modem error and after say Write command error.
-Last thing i tried was flashing stock ROM (lastest V11.0.2 and V10.0.2) via fastboot on EDL mode, but it gets endless flash modem (see image = https://i.imgur.com/BuT3rIl.png)
At moment, my phone doesnt boot anymore even at recovery or normal fastboot, only via EDL. I think its something related to modem files, but i dont know how to format or recovery the partition that have modem installed.
If someone can really help, i will be really thankfull!!
Have you tried using another usb port/cable? If you are using USB 3.0 port than try it on USB 2.0 port as 3.0 have sometimes issues. Also try re-downloading your ROM.
Please use emmcdl tool and try to flash stock rom from there. Worked for one of my friend.