I had downloaded several 64bit oreo roms and tried to flash them, but it always ended with this error message "updater script ended with error: 255". I dont know how to fix this... Please help me out....
Rom with this error :-
1. LOS 15.1
2. AEX 5.1
3. Firehound 4.1
4. Nitrogen OS
Note : Only Pixel Experience and Colt os (Both Oreo) managed to flash and boot on my device (potter)
do a full restore from the stock latest xml.zip, sounds like some partition issies.
also, idk if this is your first TWRP error, but it usually helps to go to advanced>copy logs and then upload said logs to the post you make
either try a stock restore with full wipe of data and everything else, or post logs so i can try and help you better than a guess
sunmughans said:
I had downloaded several 64bit oreo roms and tried to flash them, but it always ended with this error message "updater script ended with error: 255". I dont know how to fix this... Please help me out....
Rom with this error :-
1. LOS 15.1
2. AEX 5.1
3. Firehound 4.1
4. Nitrogen OS
Note : Only Pixel Experience and Colt os (Both Oreo) managed to flash and boot on my device (potter)
Click to expand...
Click to collapse
I also have same error 225
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
josephelsave said:
I also have same error 225
Click to expand...
Click to collapse
But i cant flash anything
---------- Post added at 06:34 PM ---------- Previous post was at 06:34 PM ----------
josephelsave said:
I also have same error 225
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
But i cant flash anything
Click to expand...
Click to collapse
I need help
Update your TWRP to the latest. That fixed the problem. For me at least.
Update Twrp
Latest version of TWRP would fix error 255
Okay I had this Problem
1st of all Install Only This TWRP Recovery
https://forum.xda-developers.com/g5-plus/development/dev-64bits-t3708091
This will solve your Problem
Now if you face error 7 then search that on youtube You will find the Solution for that, Its really easy
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.
Murrfk said:
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.
Click to expand...
Click to collapse
It helps: if you are confused don't flash anything to your phone!
Deleted - Was responding to an outdated post.
---------- Post added at 04:31 PM ---------- Previous post was at 04:18 PM ----------
nicolap8 said:
It helps: if you are confused don't flash anything to your phone!
Click to expand...
Click to collapse
???? I was merely raising the issue of space as appearing relevant to this issue. If you have any done any research or understanding of this, you would know most are treating it as a corrupt backup file. My experience was that it was not, as evidenced by the fact that once I freed space on my SD card by an internal format of it, the backup that did not work previous to the format worked fine. No data was corrupt.
Related
Hello,
So I realize their are opther post similar to this one, but nothing that fits my symptoms. I have a Xoom WiFi, rooted, with Tiamat Kernel 2.1.0 (Tachi). So far I have unable to get the ROM Manager or Recovery Mode to mount my SD Card.
When I reboot into Recovery Mode I get an error that says "E: unknown volume for path [/sd-ext]". I tried many different things to resolve this, including trying to use the option to format the SD Card. I have tried 2 SD Cards, a 4GB and a 32GB. Both cards work in the Xoom in regular mode, just not in Recovery Mode.
When I tried to format them with Recovery Mode, after I selected my options, it said "Waiting to Mount SD Card", it failed and rebooted.
So now I don't believe there is a problem with the formatting, just a problem with the mounting.
Is there something simple I am missing. If I can't get this working, I will not be able to transfer files to the Xoom if I screw something up, so I don't wont to go any further until I get this resolved.
Any help for the Noob. Thanks
Krpto1973 said:
Hello,
So I realize their are opther post similar to this one, but nothing that fits my symptoms. I have a Xoom WiFi, rooted, with Tiamat Kernel 2.1.0 (Tachi). So far I have unable to get the ROM Manager or Recovery Mode to mount my SD Card.
When I reboot into Recovery Mode I get an error that says "E: unknown volume for path [/sd-ext]". I tried many different things to resolve this, including trying to use the option to format the SD Card. I have tried 2 SD Cards, a 4GB and a 32GB. Both cards work in the Xoom in regular mode, just not in Recovery Mode.
When I tried to format them with Recovery Mode, after I selected my options, it said "Waiting to Mount SD Card", it failed and rebooted.
So now I don't believe there is a problem with the formatting, just a problem with the mounting.
Is there something simple I am missing. If I can't get this working, I will not be able to transfer files to the Xoom if I screw something up, so I don't wont to go any further until I get this resolved.
Any help for the Noob. Thanks
Click to expand...
Click to collapse
What version of clockworkmod recovery are you using? Version 4.0.0.4 does not recognize the external sd card. If you are attempting to boot into recovery through rom manager it probably 'updated' your recovery to the 4.x version.If you want to be able to access your micro sdcard in recovery, you need to flash the solarnz CWM 3.2.0.0 R4c recovery from http://forum.xda-developers.com/showthread.php?t=1074979.
Thank you for the quick reply. I think I had just found that posted elsewhere too. Its good to know its not a problem with my system, but why was hat feature removed. Just obsolete?
And Yes, it is 4.0.0.4.
Thanks Again
---------- Post added at 08:17 PM ---------- Previous post was at 08:11 PM ----------
Just a follow-up question. If I can't mount the SD Card within thsat version of Recovery, how are you supposed to transfer files onto the Xoom if you are trying to fix a screw and the system won't boot?
If I plug the Xoom into my computers USB while in Recover Mode, it mounts the Xooms drive, but won't allow me to access it. Am I supposed to be able to make that happen?
Krpto1973 said:
Thank you for the quick reply. I think I had just found that posted elsewhere too. Its good to know its not a problem with my system, but why was hat feature removed. Just obsolete?
And Yes, it is 4.0.0.4.
Thanks Again
---------- Post added at 08:17 PM ---------- Previous post was at 08:11 PM ----------
Just a follow-up question. If I can't mount the SD Card within thsat version of Recovery, how are you supposed to transfer files onto the Xoom if you are trying to fix a screw and the system won't boot?
If I plug the Xoom into my computers USB while in Recover Mode, it mounts the Xooms drive, but won't allow me to access it. Am I supposed to be able to make that happen?
Click to expand...
Click to collapse
I think it is for phones that have only one sdcard (external) and only a really small amount of internal storage. Tablets have an internal sdcard and this is whhat version 4.x reads and writes to. In addition, some tablets, like Xoom have an external sdcard and therefore require a custom recovery to take advantage of it.
There is also a newer recovery based on the cwm 4... series that is built specifically for the xoom/honeycomb' and that does read the sd... I've found it much more user-friendly... search for rogue recovery,you won't br disappointed
Re: rom manager, my recommendation is to uninstall it... seems to cause more probs than it is worth, and with the new roms' automation of boot into recovery and the ease os use of rogue recovery, there really isn't a need for it.
Very nice. Now I think I understand, and I have already switched over to the Rogue Recovery and it is working great. I like the ability to mount the SD card or switch to the internal storage. Now I feel better, and as someone else said, I do like seeing that Rogue graphic on my zoom!
Thanks again for the help!
hchxoom said:
There is also a newer recovery based on the cwm 4... series that is built specifically for the xoom/honeycomb' and that does read the sd... I've found it much more user-friendly... search for rogue recovery,you won't br disappointed
Re: rom manager, my recommendation is to uninstall it... seems to cause more probs than it is worth, and with the new roms' automation of boot into recovery and the ease os use of rogue recovery, there really isn't a need for it.
Click to expand...
Click to collapse
@hchxoom--You are right and that version may be a good option, but it seems the problem right now is that he can't boot into the os, can't access the external sdcard with flashable files and maybe a nandroid backup and the Xoom can't be accessed via adb/fastboot...
@krpto1973--Is this right? I'm a bit unclear about your current state.
Oh sorry, no. I saw that situation you described and was worried about doing anything further if I couldn't mount the SD Card. So I wanted to find a way to mount it in recovery so that i could feel more comfortable messing around. I am not as familiar with ADB commands as I should be, so I also wanted the SD Card option.
But thank you again for the quick response! you guys rock!
Krpto1973 said:
Oh sorry, no. I saw that situation you described and was worried about doing anything further if I couldn't mount the SD Card. So I wanted to find a way to mount it in recovery so that i could feel more comfortable messing around. I am not as familiar with ADB commands as I should be, so I also wanted the SD Card option.
But thank you again for the quick response! you guys rock!
Click to expand...
Click to collapse
OK, cool. Glad you got your answers.
Hello all, I've tried enough different roms to flash trough CWM and TRWP (2.6). But every time I get the error unable to open zip. And then it fails. I have unmounted my micro sd card. But that won't work, I hope people can help me here !
YouriVLD said:
Hello all, I've tried enough different roms to flash trough CWM and TRWP (2.6). But every time I get the error unable to open zip. And then it fails. I have unmounted my micro sd card. But that won't work, I hope people can help me here !
Click to expand...
Click to collapse
Hi,
Look HERE
Try PhilZ recovery.
Make sure you choose the correct variant of the phone.
Use the "Clean phone for new ROM "option.
If it fails ,try again from scratch.
Sometimes it takes a few goes.
malybru said:
Hi,
Look HERE
Try PhilZ recovery.
Make sure you choose the correct variant of the phone.
Use the "Clean phone for new ROM "option.
If it fails ,try again from scratch.
Sometimes it takes a few goes.
Click to expand...
Click to collapse
Hey I've tried this 10 times but it didn't work .
Hi, try downloading the ROM onto your internal storage and flashing that way. If it works, then you may have a problem with your sd card
---------- Post added at 02:05 PM ---------- Previous post was at 02:02 PM ----------
sbouzyk said:
Hi, try downloading the ROM onto your internal storage and flashing that way. If it works, then you may have a problem with your sd card
Click to expand...
Click to collapse
I mean make a folder on your internal storage called 'ROMS' or whatever
Download your ROM on your computer and using your preferred file explorer, transfer the zip into the ROMS folder you made earlier in your internal storage.
Boot into recovery and Factory Reset, then flash zip from your internal storage.
If this works, then you may have a problem with your external sd card
Ive used the app before : https://play.google.com/store/apps/...utm_source=42matters.com&utm_medium=WidgetWeb
It says I already have access, im rooted, safe strap, on the NC2 leak, cant even get the file manager to transfer my files from the internal storage to the external SD, I think it has to do with the problems that the internal storage has a "emulated" internal sd card so the app thinks the phone already has sd card access If someone can help that wold be greatly appreciated as I have a decent amount of media I want off my internal, god HD video takes up to much space, not to mention music and a thousand or so photos
You're on the nc2 odex, not the deodex?
<Note3>
---------- Post added at 01:21 AM ---------- Previous post was at 01:17 AM ----------
If you just said yes, go to post #164 in the nc2 rom thread. There's a link for the fix.
<Note3>
The patch you listed makes a second path that is fully writable. Use:
"/mnt/media_rw/extSdCard"
instead of:
"/mnt/extSdCard"
Hope this helps. My Tab is working perfect with 4.4.2. Still need to get my Note updated!
I'm pretty sure I flashed the deodexed one but can't be sure as I downloaded both.
I'm not sure what you mean with your mount command can you explain please
Bump for more help? Please
I'd like to know this too, as I am using nc2 firmware (stock, just root).
My device is n9005...
What he means is when copying files, use the first path he listed instead of the second path.
I set my SD card to adoptable storage, all works great except TWRP. I cant flash any zip I download because TWRP doesn't see the adoptable storage. Anyone else notice this or have a workaround?
I'm having the same problem. But I've found a workaround : put your files to /data/media/0/ and flash from there. But it's still a workaround... Waiting for adoptable storage support
Sabissimo said:
I'm having the same problem. But I've found a workaround : put your files to /data/media/0/ and flash from there. But it's still a workaround... Waiting for adoptable storage support
Click to expand...
Click to collapse
Would that put it on the SD card or the phone's storage? Also, if you wipe /data, wouldn't the files in /data/media get wiped too?
Also, another workaround is to sideload.
It's on phone's storage, and I think data wipe will wipe it. But that's the only option now) Sideload does require PC, I'm used to do everything on phone itself))
Oh, another suggested workaround is to use OTG if you have that handy.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
Sabissimo said:
It's on phone's storage, and I think data wipe will wipe it. But that's the only option now) Sideload does require PC, I'm used to do everything on phone itself))
Click to expand...
Click to collapse
Are you having to wipe the SD card everytime you flash a different ROM with adoptable storage? Found that out the hard way myself last time, and just wanted to make sure it's a consistent issue, and not something I messed up.
Stryder5 said:
Oh, another suggested workaround is to use OTG if you have that handy.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
Are you having to wipe the SD card everytime you flash a different ROM with adoptable storage? Found that out the hard way myself last time, and just wanted to make sure it's a consistent issue, and not something I messed up.
Click to expand...
Click to collapse
Can you confirm OTG would work while having adoptable storage? That could be great
I can't even get my adaptive storage to work anymore after switching roms,it crashes everytime after like few min (when formatting) when I reboot my sdcard shows as 15MB and have to format it in my pc lol
@Sabissimo
I had accepted that this was a bug and was forced to format as portable even tho I didn't want to. But I obviously need to be able to flash zips and make and restore nandroid backups.
I continue to look daily in hopes there will be a fix and this adaptable storage option in MM will be as we originally thought it would.
Has there been any other news on this?
Has anyone figured a work around, other than otg? That's is if it even works bec iv seen a lot of users saying otg did not work.
This is SUCH a let down. I also bought the 16gb purposely as someone else said.
I'm at least hoping there's a workaround that I just haven't heard of yet, that works.
This sucks.
Happy new year everyone[emoji20]
Sent from my XT1575 using Tapatalk
Hi guys, this is a really important question and any help would be much appreciated.
I have a smg360h
So, about 5-6 months ago when the cm roms came for this phone i flashed cm 12 instantly and then migrated to cm 13 when it became 'stable'. Since then my phone has became laggy as ****, ive litterally formatted and installed roms and also the stock firmware hundreds of times. I've tried all roms; from the stock firmware to cm 11 to 12 to 13 to even resurrection remix, I've tried both the recoveries(twrp and philz touch) and all of their versions. Ive tried all of the available kernels and i've tried all these things multiple times with different combinations but nothing seems to work. I have also tried @doesntexits guide to fix this issue and again, that doesn't work either. I am in need of help asap
Please help me in resolving this issue. :crying: :crying: :crying: :crying:
okay, here some suggestion, go buy a new phone dude, this phone is so old
https://drive.google.com/file/d/0BzWikRa31-8qOHJKdWVDdk90THM/view?usp=drivesdk
link of kenrnel for cm13
instruction
1. don't enable zram
2. change governor to interactive
3. use L speed.
i think your problem will be solved.
romgharti said:
https://drive.google.com/file/d/0BzWikRa31-8qOHJKdWVDdk90THM/view?usp=drivesdk
link of kenrnel for cm13
instruction
1. don't enable zram
2. change governor to interactive
3. use L speed.
i think your problem will be solved.
Click to expand...
Click to collapse
Is it good to nand erase in odin??
romgharti said:
https://drive.google.com/file/d/0BzWikRa31-8qOHJKdWVDdk90THM/view?usp=drivesdk
link of kenrnel for cm13
instruction
1. don't enable zram
2. change governor to interactive
3. use L speed.
i think your problem will be solved.
Click to expand...
Click to collapse
1 : what is the difference between this one and the CM 13 version .
2: where to do those instructions ? at which interface we are going to choose L speed and zram....etc
how long to wait for 14 cm?
and whether the stability of the 13 cm beta 4
---------- Post added at 06:00 PM ---------- Previous post was at 05:53 PM ----------
whether resurrection remix on the basis of 13 cm beta 4?
romgharti said:
https://drive.google.com/file/d/0BzWikRa31-8qOHJKdWVDdk90THM/view?usp=drivesdk
link of kenrnel for cm13
instruction
1. don't enable zram
2. change governor to interactive
3. use L speed.
i think your problem will be solved.
Click to expand...
Click to collapse
Will that kernel work on cm 12 or resurrection remix? Because some of my favorite apps dont work on marshmallow(lemme know if you have a solution for that) but I'd still let those apps go for a smooth phone. And how to do what you said?
Here is your ans-:
I had same problem 1month ago my phone was laggy when i open youtube,playstore or any other app it takes 5 min to open keyboard also not open suddenly so install twrp recovery click wipe then advance select all except micro sdcard you have to do this wiping process for 2 to 3 times like when 1st time wipe done do it again. Then install orignal rom via odin all lag gone.
AbdoRefky said:
1 : what is the difference between this one and the CM 13 version .
2: where to do those instructions ? at which interface we are going to choose L speed and zram....etc
Click to expand...
Click to collapse
Hammad1029 said:
Will that kernel work on cm 12 or resurrection remix? Because some of my favorite apps dont work on marshmallow(lemme know if you have a solution for that) but I'd still let those apps go for a smooth phone. And how to do what you said?
Click to expand...
Click to collapse
i don't try on cm12. it is specially designed for cm13
romgharti said:
https://drive.google.com/file/d/0BzWikRa31-8qOHJKdWVDdk90THM/view?usp=drivesdk
link of kenrnel for cm13
instruction
1. don't enable zram
2. change governor to interactive
3. use L speed.
i think your problem will be solved.
Click to expand...
Click to collapse
1 : what is the difference between this one and the CM 13 version .
2: where to do those instructions ? at which interface we are going to choose L speed and zram....etc
Is there anyone who still on cm12? Im asking for the tiny_hw.xlm . If u still on, plz send me that file (go to /system/etc).
Very appreciate.
AbdoRefky said:
1 : what is the difference between this one and the CM 13 version .
2: where to do those instructions ? at which interface we are going to choose L speed and zram....etc
Click to expand...
Click to collapse
Kernel auditor, maybe
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
boanhdaytien2 said:
Is there anyone who still on cm12? Im asking for the tiny_hw.xlm . If u still on, plz send me that file (go to /system/etc).
Very appreciate.
Click to expand...
Click to collapse
For what?
AnToan
Please help me! I use SM G360H CyanogenMod ROM I like to use, but I put CM13 or CM11 khi CM12.1 lost wave, normal use Reboot. Constantly Occurs có situation. Explain to me. thank XDA
@anonymous94 said:
Kernel auditor, maybe
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
For what?
Click to expand...
Click to collapse
The file got the sound quality I needed, pretty intricacy to explain but that file is sort of sound kernel which I really need but Im too lazy to go all the way back(install the cm12 again) and copy the file(cause it dont show in the zip file).
boanhdaytien2 said:
The file got the sound quality I needed, pretty intricacy to explain but that file is sort of sound kernel which I really need but Im too lazy to go all the way back(install the cm12 again) and copy the file(cause it dont show in the zip file).
Click to expand...
Click to collapse
use TWRP to flash this Kernel
forum.xda-developers.com/galaxy-core-prime/development/kernel-vegito-kernel-1-2-02-april-2016-t3350202
i just installed it in 2 minutes and much faster than the CM default one .
AbdoRefky said:
use TWRP to flash this Kernel
forum.xda-developers.com/galaxy-core-prime/development/kernel-vegito-kernel-1-2-02-april-2016-t3350202
i just installed it in 2 minutes and much faster than the CM default one .
Click to expand...
Click to collapse
let me try, hmm but u r quite wander from the subject, I said sound quality, not speed. but im gonna try it anyway, thanks for the tips
AbdoRefky said:
use TWRP to flash this Kernel
forum.xda-developers.com/galaxy-core-prime/development/kernel-vegito-kernel-1-2-02-april-2016-t3350202
i just installed it in 2 minutes and much faster than the CM default one .
Click to expand...
Click to collapse
Is it for cm12?
Hi everyone, I am here to ask if there is any way to do the Root in my galaxy core prime running the version of android 5.0.2 and if it is possible root in it without pc I hope Answers ...
Disclaimer: I am not responsible if you break your phone, lose your files, etc If you decide to perform any of my procedures you do so at your own risk...
Here's your possible fix: Using TWRP do the following:
WIPE > Advanced Wipe >
Check:
* Dalvik Cache
* System
* Data
* Internal Storage
* Cache
do NOT check "extSdCard, unless you also want to format your external SD card memory card (you will lose all photos, files, etc from your external removable Micro SD card IF you check this last option.
***WARNING***
Checking Dalvik Cache, System, Data, Internal Storage and Cache WILL also wipe out all your personal data, including pictures from the Internal memory, so perform backups to your PC as necessary before undergoing this procedure.
After you have done that you will flash the stock ROM or the rooted stock ROM that hopefully you already have the .zip saved on the Micro SD card, if now, then take out the Micro SD card and place it into your Micro SD card to SD card adapter, insert it into your computer/laptop/SD Card reader/writer and copy the .zip file of the ROM you want to install then take out the Micro SD card from the adapter and place it back into your phone, reboot the G360H back into TWRP recovery, flash that .zip (the ROM) once done reboot to SYSTEM and see if the problem (the laggyness you claim, etc) is finally fixed.
Performing the above stated procedures have helped me fix numerous phones of varying models and brands leaving them exactly working like factory specification, back to speeds, etc UNLESS the phone is experiencing NAND flash wear, in which case you will notice speed performance issues when performing Write and in some cases Read cycles, in which case I would then invest TIME into figuring out installing the ROM directly into the Micro SD card and making the phone boot from the External SD card (you will have to research this, Multi ROM might help you if compatible for your model, other solutions, etc)
FNetV1 said:
Disclaimer: I am not responsible if you break your phone, lose your files, etc If you decide to perform any of my procedures you do so at your own risk...
Here's your possible fix: Using TWRP do the following:
WIPE > Advanced Wipe >
Check:
* Dalvik Cache
* System
* Data
* Internal Storage
* Cache
do NOT check "extSdCard, unless you also want to format your external SD card memory card (you will lose all photos, files, etc from your external removable Micro SD card IF you check this last option.
***WARNING***
Checking Dalvik Cache, System, Data, Internal Storage and Cache WILL also wipe out all your personal data, including pictures from the Internal memory, so perform backups to your PC as necessary before undergoing this procedure.
After you have done that you will flash the stock ROM or the rooted stock ROM that hopefully you already have the .zip saved on the Micro SD card, if now, then take out the Micro SD card and place it into your Micro SD card to SD card adapter, insert it into your computer/laptop/SD Card reader/writer and copy the .zip file of the ROM you want to install then take out the Micro SD card from the adapter and place it back into your phone, reboot the G360H back into TWRP recovery, flash that .zip (the ROM) once done reboot to SYSTEM and see if the problem (the laggyness you claim, etc) is finally fixed.
Performing the above stated procedures have helped me fix numerous phones of varying models and brands leaving them exactly working like factory specification, back to speeds, etc UNLESS the phone is experiencing NAND flash wear, in which case you will notice speed performance issues when performing Write and in some cases Read cycles, in which case I would then invest TIME into figuring out installing the ROM directly into the Micro SD card and making the phone boot from the External SD card (you will have to research this, Multi ROM might help you if compatible for your model, other solutions, etc)
Click to expand...
Click to collapse
Stock rom is .md5,, how can i get .zip file?