Hello, I have bought and sold a few phones and flashed custom roms, run adb and fastboot etc. So although I class myself as a noob I do have some experience.
Well I recently bought a Huawei Enjoy 5 that will not boot into Android thinking it would be a nice little project, the seller said he tried to flash ios onto it and in the process deleted the system files.
It will boot into the bootloader and stock recovery and I can use adb and fastboot. If I just press the power switch it will boot to a splash screen and stop.
The bootloader is unlocked.
The model is Huawei TIT-TL00
The Build Number is TIT-TL00C01B133
I can't find a vendor country but assume it to be UK or EU.
There is not an awful lot of info for these phones but I did read they are similar to other models, Honor 5X Play, Holly 2 Plus and Y6 Pro but I don't want to flash the wrong rom.
I have managed to download a few stock roms but not C01B133. I have B122, B132 and B202h which are all for that model. But I read downgrading can hard brick them.
I also read that to flash the rom you have to extract the zip and then look in the extracted folder for the UPDATE.APP file. I can't find that file so think I am doing something wrong but I'm not sure what.
Any help would be great. If I can just get the UPDATE.APP file I would try to flash the rom but I don't know where to look.
Many thanks
Amazingly I managed to flash a Rom on this tonight. B203 official Rom. Extracted all the files and although they looked nothing like the files everyone describes I installed the dload folder onto the sd card and gave it a go. It flashed a Chinese Rom with all sorts of bloatware but no Google so I assume it is for the Chinese market. And the time on the screen was Chinese time. Luckily there was an English option to select so I spent some time setting it up. However it won't recognize any SIM and I'm not sure why, but at least it's running Android now.
Unfortunately I couldn't get any further with this because when I installed the rom it relocked the bootloader. So unless someone has any success getting them unlocked then I'm stuffed.?
Related
Hi,
I'm currently waiting for my Xiaomi device and I have some questions before rooting the phone and doing some other mods.
First of all I'll mention that I've got huge experience in flashing roms, modding etc (just not with Xiaomi), so you don't have to use noob-friendly language.
1)I bought the "Pro" variant, with 16MPx, sdcard expansion and snapdragon 650.
So can I flash any rom that is included in this section: http://forum.xda-developers.com/redmi-note-3/development or is there a difference between Redmi Note 3 Snapdragon & Note 3 Pro?
According to this thread: http://forum.xda-developers.com/redmi-note-3/development/snapdragon-note-ensure-threads-titled-t3351620 it's the same, but I just want to be 100% sure as I just bricked my previous device by flashing a wrong ROM (from other device)
Oh, and I hope the storage option doesn't really matter for ROM flashing, right?
2)I've seen some 2 methods of unlocking bootloader. First one is official, where we sometimes have to wait for some longer time to get the code and the second one is unofficial.
Are there any (dis)advantages using both of the methods, and do I have to use developer ROM to unlock it the official way? Which one is safer?
3)In case my phone would be stuck in a bootloop, can I use MiFlash to repair it?
Do I need to have modified boot.img to do this?
4)Let's assume I have China ROM stable edition. Will I be able to install via update menu the dev version (with locked bootloader) and obtain root by doing this?
5)Can I use FlashFire to flash any zip (of course not a ROM), like some audio mods etc, or am I only allowed to install Xposed with it?
6)Let's say I just flashed a ROM through TWRP but forgot to delete the emmc_appsboot.mbn file. I didn't reboot the phone yet. Will flashing a new ROM (with deleted file), restoring old backup or just deleting the file from system partition (If it exists there) prevent it from bricking?
7)What's with the modified boot.img? I don't quite understand what it's for and when to use it.
Ok, so I think that's all for now. I know these are a lot, but I just want to have some basic information about the phone before I start rooting it.
If you know some good threads that will answer my questions, please post them as an answer.
1.you can't use roms from Redmi Note 3 for Redmi Note 3 PRO;they have differnt CPU;first is equipped with an Mediatek CPU,second one is equipped with an Qualcomm CPU
2.safer method is official method;but why you need this;look around and you will see many people screaming after unlocking BL,installed TWRP,so on and finally BRICK.So my advice:Stay Safe.MIUI OS offers to you all what you needersonalization,good battery life,speed,security.Additionaly unfinished roms and not fully tested software can damage hardware of device
3.you can use MIFlash to repair device,it does exist many guides here or on MIUI Forum
4.yes you can;from China stable----->China developer and from Global stable------>Global developer;this is the order
5.i suppose that ,when you have BL unlocked and root acces,it might be possible
6.i guess not because files chianges occur after OS reboot
7.http://forum.xda-developers.com/showthread.php?t=2587462
1) If you're on the Pro, you're on the Pro. You can only flash for that specific model. The PRO have Snapdragon cpu/gpu, and the non pro version have Mediatek, which make it completely different device. Always be sure that you flash roms that have KENZO in their filename. If you flash ROM made for Mediatek, you'll possibly have a 180 grams brick.
2) I'm still waiting for official unlock code, but after 11 days still haven't got it. Unlocked it by the unofficial way and because I wasn't aware what bastards Xiaomi are, I'v managed to hard brick it so I had to open it and use the two pins for flashing. Please follow the guides in here. The disadvantage of the unofficial way is that EVERY time before you flash new rom, you have to open the archive of the rom, enter the firmware-update folder and delete the emmc_appsboot.mbn. Failing to do that will get you with locked bootloader and the only way to fix the device is by the method I've used (the story above).
3) Better reflash with TWRP. I haven't used any other tool since unlocking the bootloader and flashing the twrp recovery
4) No
5) Yes
6) No. You've already overwritten the mmc_appsboot.mbn the first time. Always check for that file and delete it before flashing. Always.
7) I don't get it also. Some people have problems with wifi without modified boot.img (kernel). Haven't got such problems by now.
ok.
So regarding the point 1. Yes, I know that there's mediatek version also.
But the link I've provided redirects to Note 3 Snapdragon forum.
The thing I wanted to know if there are only 2 types of devices:
a)mediatek, 13mpx, no sdcard,etc
b)snapdragon,16mpx, sdcard
c)snapdragon, 13mpx, no sdcard - it does not exist right?
So for eg. this rom: http://forum.xda-developers.com/redmi-note-3/development/rom-resurrectionremix-v5-6-7-xiaomi-t3365872 is for option b right?
Regarding #2. If I unlock the bootloader official way, do I also have to delete emmc... from the zip before flashing?
#2. Ok, so if I don't get TWRP, how may I backup the whole ROM?
As we know flashing some zip files, or even android itself may not boot after some time. So is there any alternative to TWRP backup (that would copy whole system)?
The snapdragon one is with 16 mpx camera and sd slot (or second sim). It comes in two variants - 2gb ram and 16 gb internal storage or 3gb ram and 32 gb of internal storage. The camera and the cpu are the same in both versions. That's why I've told you to only flash roms that have Kenzo in its name
For non rooted devices,it does exist MI PC Suite for create backup/restore from back-up
Exactly see the fourth question getting different answers.
Too many threads, conflict.... Answers,... ****ty bootloader, my advice if u don't understand things ,don't go 4 unlock.
Dont buy if you not yet ordered
Why not?
I'll receive it on monday probably, so it's too late anyway.
the thing is, that I like modding the phones and unlocking bootloader in Xiaomi will be just a matter of time, that's why I want to learn some basic stuff about this phone.
Because he hadn't read what all the guides say and then end up with hard bricked devices
The phone is a beast.
Yeah, you're probably right. I hope the N3PRO will be at least as good as my z2
Could you tell me one thing. Do I need to delete emmc... file from zip, when I've unlocked the phone official way?
Edit: I think I've got my answer here: http://forum.xda-developers.com/showpost.php?p=66618701&postcount=5
After official unlock, you should be able to do whatever you like. I'm still on the unofficial way, but got unlock permission today. Will let you know what is going on tomorrow (probably, if I have time to reflash).
Hello,i have only recently started playing with my phone and ive hit a wall and im trying to find the stock firmware for my model but i cannot,since i followed many outdated guides and guidelines my os is deleted
and although i can use stock recovery or twrp when i try to flash the update.zip i though was the correct one i get error 7 cannot update from update.zip,if i try the stock recovery i get failed at 11% with reason update missing although i placed the .app in the dload in the root of the sd card!
My device is a Huawei P9 lite VNS-L21C432B380 and i would appreciate if someone can point me to its stock firmware and any extra tip to get my bearings as to how i can reverse the bricking i caused to my phone
Thanks in advance!!!
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
OK, I'm at my limit here. I've been tampering with this phone a lot of time, I have it since 2016. Right now I'm not using it but I wanna give it away as a gift. The thing is, when I turned it on, it didn't detect the SIM card, so I wanted to flash the Stock Rom back to see what would happen. I did that, same deal.
So now the phone boots up, but I have no way of making calls, receiveing messages, etc.
Here's the list of things that I did:
Unlocked Bootloader
Rooted (right now I'm unrooted)
Installed TWRP 3.0.2.0 recovery.
Flashed all kinds of new custom ROMs
Installed Stock ROM via EMUI microSD (dload folder method)
Installed an unpacked Stock ROM (UPDATE.APP) via fastboot
I hope I can fix it somehow, I've tried installing other ROMs, taking out the SIM card and testing other ones, testing different versions of TWRP, ADB sideloading, blahblahblah. Any help is appreciated, as every thread that I find about this phone is extremely outdated and most links are down.
PD: Phone is a Huawei y6 SCL-l03 from Argentina, I use it with Telefonica, Personal company.
If it helps: when I tried to manually install the UPDATE.APP from the stock ROM via fastboot, the "CUST.IMG" failed to "write". I heard it has to do something with the kernel, I have absolutely no idea. OS worked anyways, just in case I reinstalled everything through EMUI.
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good: