Database Info

stock i1920T

i tried to put custom rom on sns but i decided to just keep it stock i want to put the original recovery that it came with so i can update in the future is it possible to update even if the bootloader is unlocked?
problem:i flashed an image but couldnt use adb with my pc.
is there a image where i can just use fastboot to flash without using adb? i was using a recovery that required me to use adb to erase some kind of sh? was stuck on that. so if theres a recovery thats doesnt need to use adb? i have a recovery but i cant flash a rom.

Are you still rooted ?

It is rooted.

If you are on stock rom already, then you can do a search using root explorer or like adao file manager for install-recovery and find it and return its name to install-recovery.sh I assume this is what you changed previously ALTHOUGH if you have CWM installed then you can probably ( and easier...ly ) just find the stock image of your phone and flash it. I just did this this morning to my phone actually..
the image for i9020T can be found here http://forum.xda-developers.com/showthread.php?t=1062777&highlight=stock+i9020t
some quick searching can probably find some other images for the different models.
once you flash one of those you may have to use fastboot to lock the bootloader back up.
"fastboot oem lock" command when connected to your phones bootloader

ive flash the zip but everything is still the same ive tried to flash with cwm v2.5.1.8 i thinks somehow this version of cwm doesnt work because i cant flash anything with this i also tried to look for install recovery.sh on adao file explorer but couldnt find it. if you can help me out would be very appreciated.

Pop out the batter of your device and tell me the model number i902......
What version of clockwork do you have?
you could try to download rom manager from the marketplace and use that to flash clockwork again. once you have done that try flashing the stock img for your model phone.. flashing zips from cwm should work.... although watch your screen when you do it see if it throws any errors

Stuck on logo after update attempt

Hello,
I tried some OTA update, and now phone is stuck on honor logo.
I don't know what to do.
I tried many methods found on internet.
Las t thing I tried is to extract BOOT, CUST, SYSTEM and RECOVERY, flash them with MultiTool -> Unbrick.
I copied UPDATE.APP via other device to the SD card /dload/.
But when I attempt with 3 buttons at the same time, it won't go to recovery. It's just stuck on logo
What else could I try?

Try this method using the latest firmware for your phone please.
Used this method for my huawei honor 7 PLK-L01.
Should work for your phone.
install latest android sdk, run it, download platform tools.
Extract boot, system, cust, recovery images using huawei update extractor from that latest firmware. Copy them to platform tools folder.
Flash them using adb command
Fastboot flash xxx xxx.img
Where xxx stands for any four of the above.
Reboot using the command
Fastboot reboot
And let it boot normally.
Copy the update.app to sd card, dload folder and use the dialer to dial *#*#2846579#*#*
Choose software upgrade, sdcard upgrade.
And let it upgarde. You will lose all your data. It will be a clean installation.
Let me know if you have any questions.

I managed to repair it just before your post but thank you very much. Hamzio7 helped me too.
I managed to enter the recovery when I flashed some other recovery version from MultiTool.
Then I was able to flash extracted images from update.app and performed factory reset.
I'm on 6.9.1.FULL now. EMUI 4.01, Android 6.
Afterwards, I flashed Open GApps, and it's all good now.
I was really frustarated with this. But, eventually, it's all good.
Thanks

bosniamaj said:
I managed to repair it just before your post but thank you very much. Hamzio7 helped me too.
I managed to enter the recovery when I flashed some other recovery version from MultiTool.
Then I was able to flash extracted images from update.app and performed factory reset.
I'm on 6.9.1.FULL now. EMUI 4.01, Android 6.
Afterwards, I flashed Open GApps, and it's all good now.
I was really frustarated with this. But, eventually, it's all good.
Thanks
Click to expand...
Click to collapse
I understand how frustrating it can be. Really happy for you. Enjoy your phone now

Accidentally wiped system partition of huawei mate 9 dualsim

Hi im new here and i need help :^;
Have a huawei mate 9 (dual sim, unlocked bootloader) and accidentally wiped the system partition through twrp (custom for huawei mate 9 through xda so not all functions work)
tried:
- fastboot flashing system.img, boot.img and revovery.img from update.zip (MHA-L29C432B176) from "techora"
--- this ended up as a boot loop
- flashing the update.zip through twrp but i got an error message for unknown command (probably because update.zip is not made for twrp)
- using dload/UPDATE.APP using ext sd card after flashing recovery.img but nothing happened, cant access internal storage so cant move the dload folder there
- hisuite system recovery but rejected my phone because it is unlocked ... tried to relock phone but still got rejected
please help ;^;
Thanks

Got it working but not optimal
how i got it working with fastboot and twrp:
flashed romaur1.5 along with system.img from a MHA-L29C636XXX full update zip
the boot img from that was a bit messed so flashed KangVIP custom rom boot.img (dont flash the whole rom there tons of chinese bloat) ---- i probably didnt need to flash the romaur, just system.img and boot.img
that fixed everthing kinda. the os booted fine but there was a messed keyboard (google voice keyboard that didnt work) so i skipped everthing and installed a google keyboard apk, then went into Settings to redo the startup things i didnt do. The other problem is that my phone is permenantly rooted with SuperSU, cant uninstall or update through the app :/ factory resetting didnt remove the root (after flashing the stock recovery.img from update.app)
Thats all..

henry931 said:
how i got it working with fastboot and twrp:
flashed romaur1.5 along with system.img from a MHA-L29C636XXX full update zip
the boot img from that was a bit messed so flashed KangVIP custom rom boot.img (dont flash the whole rom there tons of chinese bloat) ---- i probably didnt need to flash the romaur, just system.img and boot.img
that fixed everthing kinda. the os booted fine but there was a messed keyboard (google voice keyboard that didnt work) so i skipped everthing and installed a google keyboard apk, then went into Settings to redo the startup things i didnt do. The other problem is that my phone is permenantly rooted with SuperSU, cant uninstall or update through the app :/ factory resetting didnt remove the root (after flashing the stock recovery.img from update.app)
Thats all..
Click to expand...
Click to collapse
SuperSU is in boot.img so you'd have to restore that to get rid of root.
You could use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To get back to your old version or get to B190. Backing up /data is recommended if you're decrypted, or backup using titanium or similar. (that's if you want to unlock bootloader again after it's done, since it does a factory reset.)
Or you could try flashing system.img directly in twrp, to the /system partition. Youd have to flash your boot.img for B176 for this though.

ante0 said:
SuperSU is in boot.img so you'd have to restore that to get rid of root.
You could use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To get back to your old version or get to B190. Backing up /data is recommended if you're decrypted, or backup using titanium or similar. (that's if you want to unlock bootloader again after it's done, since it does a factory reset.)
Or you could try flashing system.img directly in twrp, to the /system partition. Youd have to flash your boot.img for B176 for this though.
Click to expand...
Click to collapse
I've tried that, and it doesnt work for me, going to try different boot.img from another post on xda

lol that didnt work because my system image was too old, i flashed a newer version of supersu and it installed systemless and uninstalled my old one

You could have just downloaded your update.zip, taken out update.app, extracted system.img and made a flashable zip.

Powerlated said:
You could have just downloaded your update.zip, taken out update.app, extracted system.img and made a flashable zip.
Click to expand...
Click to collapse
cant be bothered, id rather just flash through fastboot

Stuck in Bootloop! fastboot OK, can't load recovery (Failed flashes?)

Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated

SuperSpasm said:
Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated
Click to expand...
Click to collapse
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.

Mannan Qamar said:
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
removed because I don't have link posting permission
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.
Click to expand...
Click to collapse
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg

SuperSpasm said:
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg
Click to expand...
Click to collapse
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
https://androidhost.ru/
Also instructions are in the zip.

Sparkrite said:
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
Also instructions are in the zip.
Click to expand...
Click to collapse
Tried downloading a rom from androidhost.ru- it had the update folder structure described,
and I put the unzipped dload folder into microSD root like the instructions said.
But pressing vol up+down+power doesn't load any update screen for me.
It just goes to bootloop again.
Is there anything else I can try?
Thanks

Bootloop after flashing TWRP

Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!

fibonazi said:
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
Click to expand...
Click to collapse
Can you flash a copy of stock recovery.img via fastboot?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Can you flash a copy of stock recovery.img via fastboot?
Click to expand...
Click to collapse
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.

fibonazi said:
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
Click to expand...
Click to collapse
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Click to expand...
Click to collapse
Actually, the problem I'm having is that twrp runs into an error and shuts down before I can do anything on it. It is stuck in an endless boot loop and is unresponsive to any button or screen presses. I have a lineage os rom, but I don't have any way to flash it right now. Is there any way to make it responsive again? Or any way to connect it to a pc?