Related
I've compiled Android and tried to flash system.img to my phone (British Nexus S i9020) and although Fastboot reports that it sends the data across OK, the write fails with a red line of text in the bootloader: "Invalid magic code 0x03"
I've tried a different system.img and I get the same error. Though, I tried flashing a radio image across and that worked fine, I flashed the old one back as well too.
I've not found much when searching, instead something suggesting that I need stock Android, well, I am on stock, with a manual upgrade from 2.3.1 to 2.3.2, 2.3.3, and finally 2.3.4, so, I'm stumped.
Has anyone experienced this before? Could you give me any clues or pointers on what it could be please?
Thanks
bumping because i'm really frustrated.
I just had this problem, i couldn't flash anything through fastboot
i tried searching for how to copy files from recovery or bootrom couldn't find a thing
but i just found it so i thought i'd research this thread and ler u know what i did
i flahed the clockwork recovery which is the only thing that worked
i went into mounts
and mounted USB storage
copied my nexus S clockwork recovery backup (available online) and restored and my phone is working agian
hope yours will too
let me know if u need help, i'll try but i am afraid i am a noob just like u
Hello,
I love my Xoom MZ602 but right now it's bricked while trying to repartition. I've faithfully executed everyone's solution, but nothing's working. Several posts say I need:
1.35-everest.reflash.sbf
which has links all round but they're all dead!! Does anyone have it? HELP
Thanks very much!!
donriner said:
Hello,
I love my Xoom MZ602 but right now it's bricked while trying to repartition. I've faithfully executed everyone's solution, but nothing's working. Several posts say I need:
1.35-everest.reflash.sbf
which has links all round but they're all dead!! Does anyone have it? HELP
Thanks very much!!
Click to expand...
Click to collapse
Thought i would try and help you out since i have some old xoom files laying around. However, i am confused about while files you need.
MZ600: 3g xoom for Verizon US called stingrayCDMA(maybe?)
MZ601: 3g xoom for GSM called everest
MZ602: 4g lte xoom for Verizon US called stingray
MZ603: WiFI only xoom called wingray
MZ603: WiFi only xoom called wingray
So the everest file you need will not work on an MZ602.
Test question is, do you have an MZ602(Stingray) or an MZ601(everest)?
Let me know, and I will see if I can find the right file.
PS: Also, what is your region/language?
urushiol said:
Thought i would try and help you out since i have some old xoom files laying around. However, i am confused about while files you need.
MZ600: 3g xoom for Verizon US called stingrayCDMA(maybe?)
MZ601: 3g xoom for GSM called everest
MZ602: 4g lte xoom for Verizon US called stingray
MZ603: WiFI only xoom called wingray
MZ603: WiFi only xoom called wingray
So the everest file you need will not work on an MZ602.
Test question is, do you have an MZ602(Stingray) or an MZ601(everest)?
Let me know, and I will see if I can find the right file.
PS: Also, what is your region/language?
Click to expand...
Click to collapse
Thanks for helping... It's definitely an MZ602 - Verizon 4GLTE. The device accepts flashing through Fastboot or RSD, but will not save anything. I think the partition table must be gone. There is NO Recovery. Someone else suggested this file would help even on the "wrong" device. Desperate at this point will try anything.
Region - USA
Hope you have something or an idea.
donriner said:
Thanks for helping... It's definitely an MZ602 - Verizon 4GLTE. The device accepts flashing through Fastboot or RSD, but will not save anything. I think the partition table must be gone. There is NO Recovery. Someone else suggested this file would help even on the "wrong" device. Desperate at this point will try anything.
Region - USA
Hope you have something or an idea.
Click to expand...
Click to collapse
METHOD 1:
If you haven't tried it already, download this http://www.mediafire.com/download/klylgjtuy42y625/HRI39.zip, extract and flash using the following fastboot method.
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
METHOD 2:
Can you flash a custom recover in fastboot or does it fail? If it fails, what exactly is the error?
If you can successfully flash a custom recovery image, try following this guide. I know it is intended for removing a "BigPart", it should be able to recreate your partition tables if you can flash recovery.
http://forum.xda-developers.com/showthread.php?t=2635282
METHOD 3:
You can also try this SBF file which is an SBF of the newest stock rom for the MZ602
http://sbf.droid-developers.org/download.php?device=24&file=710
IF NONE OF THIS WORKS
I have searched high and low and can't find a copy of the 1.35-everest.reflash.sbf, however i understand what you were thinking, i found many people talking about this file as a method for recovery. If non of my methods above work, maybe someone still has the everest sbf in question laying around.
Please help to restore old xoom
Please help restore old Xoom mz600. It stuck in moto logo.
Recovery doesn't work too, stuck in "Reading ODM fuse: 1".
After long investigation I get it is problem with bootloader.
Maybe somebody still have this magic file 1.35-everest.reflash !!!
1.35-everest.reflash.sbf
Finally I found these files, thank you KidJoe:
1.35-everest.reflash.sbf
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
My xoom comeback to live!!!
If somebody need it, send the message I will share it.
kleralexi said:
Finally I found these files, thank you KidJoe:
1.35-everest.reflash.sbf
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
My xoom comeback to live!!!
If somebody need it, send the message I will share it.
Click to expand...
Click to collapse
please send 1.35-everest.reflash.sbf to me,thank you very mach!
emil:[email protected]
kleralexi said:
Finally I found these files, thank you KidJoe:
1.35-everest.reflash.sbf
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
My xoom comeback to live!!!
If somebody need it, send the message I will share it.
Click to expand...
Click to collapse
Why not share it in the public thread? lets be honest you won't be here to respond to stuff forever so you might as well drop a link in the thread for future collectors everywhere. And PLEASE use Android File Host, it seems to keep files forever and i don't see it going down anytime soon.
links to files
1.35-everest.reflash.zip
HRI39.zip
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.zip
thank you very much !
thank you very much !
i decided to put EVERYTHING for this phone under one roof.. the drivers, root, roms, tweaks, tutorials, links etc etc, all consolidated in one spot.. this way, anyone that bought or buys this phone dont have to scour the interwebs to find what theyre looking for. normally, its fair to assume if youre here, you have some degree of knowledge about everything to follow. however, im going to over simplify some or eventually most stuff for, example, family or friends that ask me to "jailbreak" their phone then have no idea what to do once i do. or, for anyone else that meets the same criteria ("budding android modders") lol. :good:
at the moment though, i dont have time to get everything up all at once, so i decided to create a placeholder and upload a rom in the meantime.. theres more to come as time permits..
ROM
deodexed
(now you can switch from "dalvik" to "art" in "developer options" without all the FCs.. the pros and cons with odex vs odexless roms goes back and fourth. having an odexed rom can make your phone a little faster, and free up more room for apps and stuff which is why most if not all phones come odexed (eventually, you can click here to see how to free up room by getting the most of your sdcard, so the free space you lose being unodexed wont really matter), but it has a few setbacks when it comes to modding your phone depending on what youll be doint to/with it now that its rooted (wil discuss more in detail later). If youre coming from another phone with a custom rom, and became spoiled by having developer options already in settings for you. or, you just wanna try art and/or have access to more features (this will later be moved when i explain how to root and setting up drivers, since debugging becomes relevant), getting the menu back is pretty simple. just open settings and go down to "about phone", then click on "software information". on the following screen click "build number" 7 times and if you did it right a popup will display welcoming you to the world of development lol. so simplified its "Settings>About phone>software info", click "Build number" 7x.. "Developer options" is now in settings again. in developer options ("settings>developer options") youll see "select runtime", where you can do just that).
added root and enabled adb root (you need to download your superuser app of choice though).
added busybox with symlinks.
fixed a few invalid permissions. (come to think, im gonna add them back jic its relevant to other carriers besides boost mobile)
and removed some useless symlinks. (come to think, im gonna add them back jic its relevant to other carriers besides boost mobile)
fixed kitkat sdcard write restriction.
this is a "rough draft", there is a few more little tweaks i wanna add (ie: once the device is activated on boost mobile, it downloads all the boost related apps, and those apps reinstall even after a fresh wipe/format/rom installation. its inconvenient if you switch carriers) but i just wanted to get a link up, this is a great phone for the price (only $40, when the HTC Vision still sells for $100 at a fraction of the performance), but it seems like there is close to zero development being done probably because of that (ie; i couldnt find 1 single rom for this device, its not exactly a well known, high demand, highly advertised device. but imho that doesnt mean the 27 or so rooted owners shouldnt have some easy options). unfortunately, even though i stumbled across the kernel source code for w5c (ironically on a LG l70 board) my laptop would probably take days to compile from source, so in the meantime ill tweak the stock image, and maybe eventually see if i can hack some cyanogenmod goodness together.. ill make this thread more professional as time progresses, as well as add an odexed version (definately the stocks version, but i might even redo odexing the right way as well, i donno yet because i dont see the benefit, its just my OCD acting up because i know LG did it half assed), and MAYBE a completly stock rom w/ no mods (which seems redundant since most people keep a "stock" recovery backed up.. but if you were like me and didnt know how easily the bootloader could be unlocked, so you just rooted and started playing with stuff, it might come in handy to have a stock rom lying around.)
Downloads
http://[email protected]/download/%75c%749%6D%6459%77%659%78sl%78/lgls620.zip
http://[email protected]/public/%42%54%44s%42%56/lgls620.zip
http://[email protected]/#!KZFkxb5K!zXW_1p_WMcR_EenrGPoLEgo_-OURR2i7tHSa6GCk5j8
MD5: cc88f51b3e483c4a8c3b974d6f87ceec
File Name: lgls620.zip
(google url shortener didnt like my link and claimed it was a TOS violation, then mediafire deleted the file claiming the same, all within only a few hours of uploading.. so i apologize for the obscured non clickable download links. i never had this problem before so i dont know what they dont like or how theyre deciding its a violation, and if i make the urls clickable xda automatically un-obscures them, so untill i figure out what they dont like or how they go about making that decision, im gonna assume its a bot. i tried an anonymous referer but then mediafire falsely claims the file was removed for violating TOS, without the referer it works fine though (completely unrelated, keep that in mind.. if you ever try downloading something on mediafire that says its been removed, and you were sent there by a referer, try reloading the mediafire link independently before giving up on the dl, i imagine they assume if your being refered anonymously its pirate related so they block you)
PLACEHOLDER
Placeholder
Placeholder
Placeholder0
Placeholder0
Placeholder1
Placeholder1
Placeholder2
Placeholder2
Placeholder3
Placeholder3
How did you unlock the boot loader?
I zeroed the laf partition and did fastboot oem unlock with fastboot oem device-info reporting:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
but when I try flashing a modified (using Android Kitchen) boot image it comes up saying:
Code:
ERROR : boot certification verify
[750] ------------------------------------------
[760]
[760] Secure booting Error!
[760] Cause : boot certification verify
[760]
[760] ------------------------------------------
I'd like to be able to change the init scripts, and possibly the kernel (where did you find the source?), but I'm stuck getting it to boot with the new image.
Laf
Zero laf, fastboot oem unlock, flash recovery, profit
soulife said:
Zero laf, fastboot oem unlock, flash recovery, profit
Click to expand...
Click to collapse
this thread will be updated soon (for those who give af)
Recover your dead LG REALM (LS620)
First of all thanks to @soulife for the deodexed rom.
2nd to @fatherguido for the boot.img
3rd to @bcrichster for the stock recovery.img
4th to @elisam98 for the bumped twrp img
This is for you all that want to recovery your dead LS620.
This applies to all phones that have no recovery/fastboot mode enabled/download only/or just a faulty rebooting system.
1. you have to enter download mode and zero out LAF partition: to do this you have to download the LG root zip and follow some steps in this tutorial (until step 10) then run the following command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
2. Power off the phone and enter download again, only this time it will be fastboot mode.
2a. here you will fastboot oem unlock command
2b. flash twrp from here
(the commands to flash this twrp img in fastboot are: fastboot flash recovery w5c_twrp_bumped.img)
3. Enter twrp and flash my backup which has the boot.img from fatherguido and the stock deodexed rom from soulife.
Or you can flash the stock deodexed rom in this forum by soulfie
and then reboot to fastboot again and flash manually the boot.img by fatherguido.
links to all files:
boot.img (zipped)
twrp.img (zipped and bumped)
LG ROOT (zipped)
Stock recovery (zipped)
My TWRP backup (7zipped)
GOOD LUCK!!!
Sweet! Nice job, bro.
Gratefully sent from my Rooted JollyRoger_B13
Alex_XV6700 said:
First of all thanks to @soulife for the deodexed rom.
2nd to @fatherguido for the boot.img
3rd to @bcrichster for the stock recovery.img
4th to @elisam98 for the bumped twrp img
This is for you all that want to recovery your dead LS620.
This applies to all phones that have no recovery/fastboot mode enabled/download only/or just a faulty rebooting system.
1. you have to enter download mode and zero out LAF partition: to do this you have to download the LG root zip and follow some steps in this tutorial (until step 10) then run the following command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
2. Power off the phone and enter download again, only this time it will be fastboot mode.
2a. here you will fastboot oem unlock command
2b. flash twrp from here
(the commands to flash this twrp img in fastboot are: fastboot flash recovery w5c_twrp_bumped.img)
3. Enter twrp and flash my backup which has the boot.img from fatherguido and the stock deodexed rom from soulife.
Or you can flash the stock deodexed rom in this forum by soulfie
and then reboot to fastboot again and flash manually the boot.img by fatherguido.
links to all files:
boot.img (zipped)
twrp.img (zipped and bumped)
LG ROOT (zipped)
Stock recovery (zipped)
My TWRP backup (7zipped)
GOOD LUCK!!!
Click to expand...
Click to collapse
hey ive been doing this for a long time now, but im still a noob to some things.....
what is a boot.img?
i always read people saying to flash it this way or that, and i see it on file hosting sites along with the stock and custom roms and recovery.img, but ive never gotten it and done anything with it because i dont know what the hell it is,what it is for, and what the point of having it is
just wondering lol
mistaweeks said:
hey ive been doing this for a long time now, but im still a noob to some things.....
what is a boot.img?
i always read people saying to flash it this way or that, and i see it on file hosting sites along with the stock and custom roms and recovery.img, but ive never gotten it and done anything with it because i dont know what the hell it is,what it is for, and what the point of having it is
just wondering lol
Click to expand...
Click to collapse
If you dont need to repair or resurrect your phone or change to a custom rom then you dont need to modify the boot.img
:good::good::good::good:
I'm stuck my lg realm ls620 only enters download mode, no recovery, and won't boot. So following your instructions in step one gets me stuck on step 2 of the thread you referred to in step 1. How can I transfer the rootedsystem file into the root of my phone if it will ONLY go into download mode? Please help.
Wazza
bcrichster said:
Sweet! Nice job, bro.
Gratefully sent from my Rooted JollyRoger_B13
Click to expand...
Click to collapse
Hey wassup remember me from the other website??
You helped me root my ZTE Z730 and made a custom
ROM for it. I got this phone now, but I'm probably not
Gonna use this ROM. I'll wait for an odexed one.
Thanks anyways!!
i recently seen a web site that says 5.0 update for lg realm is this a legit rom or a fake
Hello XDA. I'm curious if anyone has any info or advice on getting working camera libraries for cm12 for the lg realm. As those from Android forums are aware, we have some cm12.1 Roms for the ls620, but they are incomplete in a few aspects.
One is cameras. Neither front or back cameras work, which I believe to be an issue with the libraries used. I don't know enough about compiling the ROM with proper Android lollipop camera libraries for this phone.
Aside from that, the Roms work pretty well. There seems to be less development for this phone which is a beast otherwise(not considering the small memory...)
Hoping someone can lend some input.
Thanks!
Hey I've bricked my lg ls620 I can get into factory reset and download mode can you instruct me on how to get it fixed or at least get twrp on it and I got it from there it's a girls phone I'm fixing for here and she has her dought that it can be done normal thing would be flash tool and kdz but the only way to get the kdz is to buy it and it may still not work I get a secure boot error
Sent from my XT1526 using XDA-Developers mobile app
hard bricked
i need to unbrick ( Qualcomm DLoader mode ) no recovery no boot. :crying:
p.d. Sorry for reviving old threats but I need it i have no phone or money to have another one :/
I'm sure there are other posts like this will be. I know - I've read probably all of them. But I am still stuck.
MHA-L29C636 phone. I rooted last night and when I was setting my apps back up, I noticed Snapchat wasn't working. A quick search told me to install XPosted Framework. I downloaded and installed it, and shortly after that, if not immediately, my phone shut off and wouldn't start.
I was at work, so I panicked. Thankfully, the eRecovery thing booted up and told me I could reinstall over WiFi. GREAT! Nope. It was not able to connect to the server. I tried a few times, reset. A few more, reset. Different network, reset.... Nothing was working. So, I did a data wipe and selected Dalvik Cache, Data, Internal Storage, Cache, System partition, and then did a factory reset. I figured that could clear out the XPosted install and I would start fresh. No, that also did not work...
So, I've searched for 6 hours since I've gotten home from work, tried countless methods and downloaded almost 20GB of images, custom ROMS, firmware files, etc. And LITERALLY almost 20GB. I keep running into issue after issue preventing me from getting anything to work.
I've installed ADB/Fastboot. That wasn't working, so I installed the full Android Studio and SDK Toolkit. Didn't get anywhere with Fastboot.
I've tried flashing custom ROM's to get SOMETHING back on my phone. Nothing will install.
I've tried doing a forced update with the POWER + VOL UP + VOL DOWN. Did not work. Gives an error of unable to update.
Then I came across HWOTA. The write ups were confusing as hell to me... but finally I understood one. Copied the 3 files to the SD card to load into the phone and went to run update.bat from the HWOTA extracted folder..... Except the batch file instantly closes and I don't get to see the screen with the numbers that EVERYONE else gets to see apparently.
HiSuite doesn't even see the phone.
I'm completely lost. I need some help. Badly.
@mankindtw I've seen hundreds of your posts. You seem pretty in the know with the Mate 9
http://www.carbontesla.com/2017/05/tutorial-rebrand-convert-huawei-mate-9-to-any-region/
https://forum.xda-developers.com/mate-9/how-to/guide-how-to-unbrick-mate-9-access-t3720953
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I was following these guides for the HWOTA procedure, and as I said, the update.bat will not execute. "...is not recognized as an internal or external command,
operable program or batch file." is the message that is created.
https://www.getdroidtips.com/huawei-mate-9-b321-oreo-firmware/
I downloaded my firmware files from here, as well as the page here on XDA.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page26
Then I came across this man showing me what I can't see with update.bat. >.>
Hopefully someone can help quickly. I'm tired of messing with this phone and I'm needing it for this weekend.
What Android's version did you have? Nougat or Oreo?
If Nougat there is quick method to unbrick.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Just do option 4 - download special service ROM for your region C636 and apply it via dload.
If your phone will boot and has no system update, then do options with installing TWRP and additional package. System update will appear and you will have ability to get new ROM.
P.s. I don't know does this method work in case with Oreo's "brick". It did not tested.
5[Strogino] said:
What Android's version did you have? Nougat or Oreo?
If Nougat there is quick method to unbrick.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Just do option 4 - download special service ROM for your region C636 and apply it via dload.
If your phone will boot and has no system update, then do options with installing TWRP and additional package. System update will appear and you will have ability to get new ROM.
P.s. I don't know does this method work in case with Oreo's "brick". It did not tested.
Click to expand...
Click to collapse
Unfortunately, it just updated to O last week. I'm wondering if that's why the eRecovery does not work as it should.
I don't know enough about the file structure of Huawei to be able to know how to reload everything back into place, brand new. I'm familiar with Samsung and Odin, but I'm trying to find out the steps for getting everything squared away.
I also realized that I'm not 100% certain that this had the C636 FW. It's a dual SIM and I believe I bought the International version instead of the US version. Would it be best to rebrand to a specific region so I at least know what it's set up for?
What is the correct process for re-flashing the file structure and files? I'd imagine what I need to do is a full format, and then reload everything from the ground up. I just don't know the correct order. Re-brand, flash new UPDATE.APP and the 3 zip files? Would I force flash the UPDATE.APP and then flash zip through TWRP?
I've thought about cutting my losses and trying out this FunkyHuawei thing, that's just a good bit of money I was not prepared to be spending, and especially for no guaranteed result. I was not looking to mod this phone at all, just root access for some monitoring apps.
I may see what an authorized service center will charge to fix it. I'd hate to keep tinkering with it and get it hard bricked.
Why don't you try FunkyHuawei? You have to buy credits though... https://funkyhuawei.club/
gioarvdv said:
Why don't you try FunkyHuawei? You have to buy credits though... https://funkyhuawei.club/
Click to expand...
Click to collapse
I had said above that it was a lot of money to invest in something not guaranteed to work. At least if I brought it to a shop, I wouldn't pay unless it were fixed.
300zxmatt said:
I had said above that it was a lot of money to invest in something not guaranteed to work. At least if I brought it to a shop, I wouldn't pay unless it were fixed.
Click to expand...
Click to collapse
I think the reason your .bat file doesn't work is where you have it placed. I had the howta folder on my desktop and it wouldn't work not matter what I did. I moved it to the root of the c:// drive and then it worked. Perhaps you should try that.
Mmm... I have to just saying: stop killing phone!
Why you are thinking that format system will help? It will kill your system partition and you will get no ability to run into normal mode anymore. Without system partition phone will not run.
Why are you thinking that rebranding will help you? You have troubles with current region. You will feed the mess while rebranding cause it will get additional troubles with metadata mismatch.
Your current goal is to get phone when it is running normal. To do that, you can apply service ROM. Service ROM is special one, it is only ROM that can be flashed via dload. Other ROMs can not be flashed this way.
5[Strogino] said:
Mmm... I have to just saying: stop killing phone!
Why you are thinking that format system will help? It will kill your system partition and you will get no ability to run into normal mode anymore. Without system partition phone will not run.
Why are you thinking that rebranding will help you? You have troubles with current region. You will feed the mess while rebranding cause it will get additional troubles with metadata mismatch.
Your current goal is to get phone when it is running normal. To do that, you can apply service ROM. Service ROM is special one, it is only ROM that can be flashed via dload. Other ROMs can not be flashed this way.
Click to expand...
Click to collapse
Alright, I downloaded that offline firmware dload zip, extracted it on my SD card all alone, and tried installing. It gave a "Software Install Failed" message just like the other times.
https://forum.xda-developers.com/showthread.php?t=2277112
Following this to get a better understanding of Fastboot and how to use it.
I tried 'fastboot erase system -w' and it returned with
"wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'system'...
OKAY [ 46.028s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.358s]
finished. total time: 46.388s"
That first bit about being unable to determine the partition type worries me a little bit. That is why I was talking about re-wiping everything and starting from scratch @5[Strogino]
Wow. I booted into TWRP and went to do the factory reset through there and it threw an error for every operation. I have a feeling that trying more things is doing more harm than good.
Edit: found out how to fix that. I went to Wipe>Advanced Wipe>Selected 'System'>'Repair or Change'> and opted for EXT4 because apparently that is the most common.
300zxmatt said:
Wow. I booted into TWRP and went to do the factory reset through there and it threw an error for every operation. I have a feeling that trying more things is doing more harm than good.
Edit: found out how to fix that. I went to Wipe>Advanced Wipe>Selected 'System'>'Repair or Change'> and opted for EXT4 because apparently that is the most common.
Click to expand...
Click to collapse
Dude you're really just making **** worse by throwing the everything and the kitchen sink at it. Inbox me or something so we can have a conversation as to your options
I agree...
shae23 said:
I think the reason your .bat file doesn't work is where you have it placed. I had the howta folder on my desktop and it wouldn't work not matter what I did. I moved it to the root of the c:// drive and then it worked. Perhaps you should try that.
Click to expand...
Click to collapse
the reason why the Batch file instantly closes is due to where you have saved it. Move it to C:\ and you should be good to go. HWOTA is by far the best method to recover your phone (in my opinion)....and even better....it's free!
rbt001 said:
the reason why the Batch file instantly closes is due to where you have saved it. Move it to C:\ and you should be good to go. HWOTA is by far the best method to recover your phone (in my opinion)....and even better....it's free!
Click to expand...
Click to collapse
Well! That got me somewhere! I never saw anywhere that I found to place it in the root directory of the drive. I guess since ADB is located there, it kind of makes sense?
Now, new issue. This is what I'm getting off the bat.
****************************************
* *
* This script is made by XDA mankindtw *
* *
****************************************
Use Vol-Dn + USB Cable to boot into fastboot mode.
Press ENTER key to continue...
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.665s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.678s
Disconnect usb cable and turn off phone, use Vol-Up and Power key to enter TWRP recovery.
Press ENTER key to continue...
Click to expand...
Click to collapse
And after this failure, it will not do anything when I attempt to follow the prompt to boot and reconnect USB inside TWRP.
Any ideas from this point? Happy to have SOME amount of progress, and glad to be learning the correct procedure!
300zxmatt said:
Well! That got me somewhere! I never saw anywhere that I found to place it in the root directory of the drive. I guess since ADB is located there, it kind of makes sense?
Now, new issue. This is what I'm getting off the bat.
And after this failure, it will not do anything when I attempt to follow the prompt to boot and reconnect USB inside TWRP.
Any ideas from this point? Happy to have SOME amount of progress, and glad to be learning the correct procedure!
Click to expand...
Click to collapse
That's easy enough, do you have Twrp installed, if not, what was your last Android version, nougat or Oreo?
shae23 said:
That's easy enough, do you have Twrp installed, if not, what was your last Android version, nougat or Oreo?
Click to expand...
Click to collapse
Yes, I have TWRP installed prior to all of this. Most recent version was Oreo. I used the "twrp_android_o_mate9_a1" file to flash TWRP.
Under C:\HWOTA\recovery\MHA, I have 3 recovery versions. I'm assuming the script flashes "MHA_twrp-3.0.3-1-hi3660" judging my the returned file size and the file size in Windows for that file. I wonder if flashing it manually would fix the issue.
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
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.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45...Eh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_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
I tried flashing the TWRP included in HWOTA and it err'd the same way. I'm assuming that like when I first installed TWRP and it didn't take the regular release, the version included and scripted with HWOTA is not compatible with O?
@mankindtw do you know anything about what my issue is with the script? TIA!
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
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.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45...Eh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_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
I tried flashing the TWRP included in HWOTA and it err'd the same way. I'm assuming that like when I first installed TWRP and it didn't take the regular release, the version included and scripted with HWOTA is not compatible with O?
@mankindtw do you know anything about what my issue is with the script? TIA!
C:\Users\Matt\Downloads>fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (26982 KB)...
OKAY [ 1.045s]
writing 'recovery_ramdisk'...
OKAY [ 0.267s]
finished. total time: 1.314s
Click to expand...
Click to collapse
Flashing the O version above works fine.
Hey guys,
so i'm having big problems updating my firmware on my 8t. After the last update i experienced some issues, Luk told me to try to update the firmware. I solved every problems, except for one:
When im trying to flash the img files, most of them are getting the error message:
Sending 'abl_a' (0 KB) FAILED (File is too large to download)
even, if the files are only 20kb large. Some 2000kb sized files just works fine. What is happening? I don't really know what im doing wrong. I have about 20-30 gb of free space on my phone, is this the problem? I hope someone can help me, im really enjoying lineageos. But my phone always crashes now and some things like sound or microphone aren't working.
Can somebody maybhe help? I', trying to do this for hours now....
I'm using this instructions https://wiki.lineageos.org/devices/kebab/fw_update
Mine1003 said:
Hey guys,
so i'm having big problems updating my firmware on my 8t. After the last update i experienced some issues, Luk told me to try to update the firmware. I solved every problems, except for one:
When im trying to flash the img files, most of them are getting the error message:
Sending 'abl_a' (0 KB) FAILED (File is too large to download)
even, if the files are only 20kb large. Some 2000kb sized files just works fine. What is happening? I don't really know what im doing wrong. I have about 20-30 gb of free space on my phone, is this the problem? I hope someone can help me, im really enjoying lineageos. But my phone always crashes now and some things like sound or microphone aren't working.
Can somebody maybhe help? I', trying to do this for hours now....
I'm using this instructions https://wiki.lineageos.org/devices/kebab/fw_update
Click to expand...
Click to collapse
Use the firmware flasher and flash the firmware.zip in recovery
adb sideload firmware.zip
Here is the link to the firmware files. Choose the latest for your specific region.
GitHub - Wishmasterflo/Firmware_flasher: Firmware Flasher script for Oneplus devices
Firmware Flasher script for Oneplus devices. Contribute to Wishmasterflo/Firmware_flasher development by creating an account on GitHub.
github.com
MeHigh.G said:
Use the firmware flasher and flash the firmware.zip in recovery
adb sideload firmware.zip
Here is the link to the firmware files. Choose the latest for your specific region.
GitHub - Wishmasterflo/Firmware_flasher: Firmware Flasher script for Oneplus devices
Firmware Flasher script for Oneplus devices. Contribute to Wishmasterflo/Firmware_flasher development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Yes! Wishmasters repo is great .
hightech316 said:
Yes! Wishmasters repo is great .
Click to expand...
Click to collapse
I know, that's why I posted it. XD