Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Try grabbing the required update files from the teammt site, using the huawei update extractor to grab the partitions you need and then manually flashing with fastboot.
I have the mate 10 pro and usually after getting into a bootloop I flash the kernel, system & recovery_ramdisk then everything starts working as it should
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
I meant for the original rom, not the 8.0 one, probably should have clarified that in my post
Raptorta said:
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
Click to expand...
Click to collapse
Well, okay.
I have the 7.0 structure of EMUI 5.1, and right now all I have is the update.zip for the 8.0 Oreo filmware of my EXACT model. I don't have hw or data.
So, I have a couple of questions...
From what I understand, you are trying to solve the problem using method 3, making it Oreo based. If so, how do I go about doing that?
Okay, sure, I can flash noCheck, but finding update, hw, and data for my model, let alone the 7.0 version is pretty hard.
Also, when I find it, what exactly do I have to do???
"Send commands to flash the files" whaaaaat??
All I have rn is adb, fastboot, and on my phone I have TWRP, eRecovery (won't work) and the update.app thingy
Maybe I could format the sdcard to ExFAT, move the 8.0 update.app and install it using the dload method?
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Raptorta said:
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Click to expand...
Click to collapse
Okay, so here goes again.
My exact build number is RNE-L21C432B137, and my region number is +972 (country).
Anyways, by "ZIPS-HERE" what do you mean? This post isn't very well explained. Sure, you did include some major details, but I can't really understand it.
Also, I'm still wondering, is the dload method still a viable option? Thank you!
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Raptorta said:
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Click to expand...
Click to collapse
Okay, could you tell me step by step, what to do?
I'm unable to format sd card. I need a reader.
Right this second, I'm on TWRP. What do I do?
In the site you've linked, I can find 6 versions of the software.
These are the names of it:
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 161084)
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 160963)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 134022)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 134021)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 133902)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 133901)
I have no idea what "v" stands for.
So, what do I download, and what do I do? Please help.
Also, could you use "English"? Meaning, explain it step by step.
Like, give examples, ect...
EXAMPLE:
Flash the custom rom using TWRP
Example:
Tap LineageOS from the selection menu in "Install" in TWRP
Swipe to install
Thank you so much!
UPDATE: I cannot download anything.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Literally, every single link I go to, nothing. This site is useless.
Do you have Discord by any chance? Talking via a forum is really inefficient. If so, send me in PM's your discord.
Related
Update:
I was able to use this method to root the new ICS update. The thread has been edited accordingly.
----------------------------------------------
I was unable to find a single thread that detailed how to root the stock T-Mobile Springboard firmware and keep the boot and recovery partitions intact to allow future updates, so I have consolidated information from other threads and posts, as well as adding a little myself. Full credit goes to the users and thread OP's referenced in the post links below.
The usual warnings apply: Under no circumstances should anyone do this to their device. You are likely to brick your device and render it completey unusable. In addition, you will void your warantee with T-Mobile. So you will have an out-of-warantee brick instead of a nice, functional tablet. Turn back now while there is still time.
Before you begin, I obviously did this to my device without any problems. My device is running full stock T-Mobile Springboard firmware with the following:
Android version: 4.0.3
Baseband version: 314007
Kernel version: 3.0.8
Build number: S7-303uV100R002C201B035
I do not know if it will work on a device with any other version of the firmware. The following also assumes that you have fastboot and ADB installed and functional on your computer.
In describing how to boot into fastboot and recovery modes below, the description of the volume buttons is how they are while in portrait mode in Honeycomb....as this is where I first used this method. In other words, the volume button closer to the power button is volume up and the other volume button is volume down.
1. Download the CWM Recovery image from this post:
http://forum.xda-developers.com/showpost.php?p=23601045&postcount=7
2. Download CWM-SuperSU-v0.95.zip from this post:
http://forum.xda-developers.com/showpost.php?p=27678611&postcount=22
3. Copy the CWM-SuperSU-v0.95.zip file to an sdcard and put the card in your device.
4. Flash the CWM recovery image to your first recovery partition ONLY:
a.) Boot into fastboot by powering down the device and starting it back up by pressing the
volume up and power buttons at the same time. After the device vibrates, release the
power button but keep holding the volume button until it is booted into fastboot.
b.) Once in fastboot, flash the recovery image:
Code:
fastboot flash recovery recovery5.5.0.4.img
5. Press and hold the power key for 10 seconds to reboot the device. It will boot into the
T-mobile firmware.
6. Power down the device in the usual fashion.
7. Boot into recovery by starting the device back up by pressing the volume down and power
buttons at the same time. After the device vibrates, release the power button but keep
holding the volume button until it is booted into CWM Recovery.
8. Choose 'install zip from sdcard' -> 'choose zip from sdcard', then select the
CWM-SuperSU-v0.95.zip file you put on your sdcard above, then confirm installation.
9. Go back to the main menu and select 'reboot system now'. It will boot into the T-Mobile
firmware.
10. Shut the device down again in the usual fashion, then restart normally and boot into the
T-Mobile firmware again.
11. Now you need to get your stock recovery partition back and get rid of CWM recovery.
There are two copies of the stock recovery- one on each 'recovery' and 'recovery2'. You can
get back to stock recovery by extracting an image from 'recovery2' and flashing it back to
'recovery'. The following (using adb from your computer) will dump the image from recovery2
to your sdcard:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard2/recovery.img
12. Take the sd card out of your device and copy this file back to your computer, then flash the
first recovery partition with this image as in step 4b above, but with your new recovery.img file.
You are now rooted and your recovery partitions are returned to stock.
Once you are rooted, if you would like to remove some of the T-Mobile bloatware note that the apk files are not in the usual location (/system/app). I found them tucked away in the following directory:
/data/cust/app
Of course, you will need an app like Root Explorer to get to them and delete them...or you can just use adb. I deleted several of the apk files in that directory, rebooted, and everything is working just fine...with less bloatware.
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Just to add another bit of information - a list of what I believe are the internal partitions and their locations appears below. I got this from the output from 'cat /proc/partitions' and 'mount', as well as further inspection of the stock recovery image that I extracted from my device. As we don't have a functional CWM Recovery, and I am not sure that I would use any version that was built for the Mediapad (i.e. non-Springboard) for backup and restoring, this list should give Springboard users a way to back up their devices. Using the 'dd' command as in the coding box at the bottom of the OP for each of the paritions should result in a partition image stored out on the sdcard. Fastboot then should be able to flash these 'backed up' images back to the device as in step 4b of the OP...with the correct partition names and backup files substituted of course. I did do this for the recovery partition as I detailed in the OP, but have not tried it for the rest of the partitions.
Code:
/misc emmc /dev/block/mmcblk0p14
/vrcb emmc /dev/block/mmcblk0p16
/recovery emmc /dev/block/mmcblk0p17
/recovery2 emmc /dev/block/mmcblk0p18
/boot emmc /dev/block/mmcblk0p19
/system ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p22
/cust ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p27
/tmpdata ext4 /dev/block/mmcblk0p23
/persist ext4 /dev/block/mmcblk0p21
/tombstones ext4 /dev/block/mmcblk0p24
/firmware ext4 /dev/block/mmcblk0p1
Thanks
Many ty's for this.
Thanks you help me rooted my Springboard. Have you try the MediaPad Phone app can we use the tablet for calling? :good:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
---------- Post added at 06:11 PM ---------- Previous post was at 05:49 PM ----------
robkaos said:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
Click to expand...
Click to collapse
Also can I do it without PC?
Sent from my SpringBoard using XDA Premium App
Can I use the recovery image from the update that is still on my sd card,what is the difference between the I've springboard .rar, and the su files
Sent from my SpringBoard using XDA Premium App
robkaos said:
Do I have to do step 11 ?
......
Also can I do it without PC?
Click to expand...
Click to collapse
If you do not return your recovery partition to stock, then you will not be able to install future firmware updates from T-Mobile as their updates rely on the stock recovery. So no, you don't have to return your recovery partition to stock, but if you don't you will not be able to install future T-Mobile updates. As far as doing this without a computer - you can use a terminal emulator on your Springboard to create the recovery image from 'recovery2'....the commands should be the same. However, you need to fastboot flash that image back to 'recovery', which you must do from your computer with your device in fastboot mode.
robkaos said:
Can I use the recovery image from the update that is still on my sd card....
Click to expand...
Click to collapse
Yes, if you extract the recovery image from the official T-Mobile update package, you can use this image to flash 'recovery' back to stock when you are done.
Some people have reported that they are unable to boot into CWM recovery if it is flashed only to 'recovery' and not also to 'recovery2'. It is my experience that the device seems to alternate which recovery partition it boots into when you sequentially boot it into recovery mode. When I have CWM on 'recovery' and the stock recovery on 'recovery2', my device will boot into CWM every other time I boot into recovery mode. The other times it boots into the stock recovery. If you can't get CWM recovery to appear when you boot into recovery mode, you could do things a bit different than the instructions. Extract the stock recovery image from the official T-Mobile update package. Store this away on your computer. Then, instead of only flashing 'recovery' with CWM recovery, also flash 'recovery2'. Once you are done rooting the device, use your stored image of the stock recovery to flash 'recovery' and 'recovery2' back to stock.
Originally, I used this method to root Honeycomb. I did not have the T-Mobile update package for Honeycomb and so could not simply extract the stock recovery image from that package. You cannot use the 'dd' command as in step 11 above until you are rooted to dump the image of 'recovery2'. So, without a copy of the update package I could not get an image of my recovery partition without already being rooted. But to root, I have to overwrite my recovery partition with CWM recovery, thereby making it impossible to dump a copy of the stock recovery as I had wiped it out and replaced it with CWM. The solution was to only flash one of the recovery partitions and keep the other one as a backup until the device was rooted and the image could then be extracted.
robkaos said:
...what is the difference between the I've springboard .rar, and the su files
Click to expand...
Click to collapse
Not sure what you are asking here...please clarify.
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?there is not a one click Method like motor defy? My phone wasn't such a problem
Sent from my SpringBoard using XDA Premium App
robkaos said:
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?
Click to expand...
Click to collapse
I don't know about the root files for the Mediapad. I know there is a package that contains the su files and a Windows-based command file that contains a string of adb commands that is supposed to work to root both the Mediapad and the Springboard. I think what you are talking about can be found at either one of these locations:
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
I tried to use this, and got a 'premission denied' fail pretty early on. I run Linux on my desktop, so perhaps this works under Windows with the specific Springboard drivers and interface software installed, but it sure does not work in Linux. I came up with my method (or rather consolidated the information for 'my' method from multiple other sources) as a result of having this root method fail for me.
robkaos said:
...there is not a one click Method like motor defy? My phone wasn't such a problem
Click to expand...
Click to collapse
If the files that I linked above work for you, then this is going to be about as close to a 'one-click' method as you can get. Unless you modified it, your Motorola Defy is running Android 2.1 (Eclair). This version of Android can be rooted pretty much just by yelling 'ROOT!' at your phone. There is even an app in the market that can be installed and run on an Android v2.1 device that provides a one-click root without the use of a computer. All of the exploits that were used for these one-click root methods were patched in Android v3+. Pretty much every device needs its own unique root method now, and the only way it is a one-click method is if someone has constructed a command script to execute all of the needed commands for you, as in the linked packages above.
xdajunkman said:
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Click to expand...
Click to collapse
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Thanks for the clarification
Sent from my SpringBoard using XDA Premium App
cmstlist said:
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Click to expand...
Click to collapse
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Just finished rooting my MediaPad from t-mobile. I had to install into recovery one and two so now I have no original recovery but I don't really care, I've got the latest Android Ice Cream update beforehand. What usefull apps with root access do I need now? I've got ad free and ROM Toolbox. Was there a phone app that I could use now?
Failed updates and can't recover - PLEASE HELP!
xdajunkman said:
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Click to expand...
Click to collapse
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
knightpawn said:
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
Click to expand...
Click to collapse
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Any particular locations for the other files via fastboot?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
Wow! Thanks for the help! I unfortunately, don't have my other computer that has the proper drivers installed to recognize the tablet and to run fastboot on. So, I'll try the fix you are suggesting once I get home today. However, in the meantime, I had some questions with regard to where I should flash the other files.
I understand that recovery.img should go to the recovery and recovery2 partitions.
What about the others? Does boot.img go to a particular partition? Effectively, what would the command line look like? (eg fastboot flash boot boot.img?)
Sorry about the newbie questions. I've installed a number of custom ROMs on phones using CWM, but this is a strange beast.
With regard to your question of whether it boots, well, kind of...it does boot to the T-mobile Springboard screen, then it sits there. I will let it sit for 20-30 minutes and see what happens. Will report back...for sure!
Thanks a ton!
[UPDATE]
So, I had a chance to install the TWRP recovery with the CM10 ROM. I loaded the CM10 ROM with the TWRP which installed successfully. I turned the tablet on and let it sit there for about 10 minutes and sure enough, CM10 runs just fine. However, I did notice that I cannot receive any calls. I am able to make calls, but when someone dials my number, it just goes straight to voicemail.
So, now, I'm wondering, if I can get the stock ICS with International ROM running so that I can try to use this thing as a phone, data and texting tab. I'll try what you suggested when I get home as mentioned earlier.
CM10 has too many problems, why would you want to use it?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
That worked for me. After playing with vold.fstab I had rendered my Springboard unusable (got the encryption was unsuccessful screen!).
I really wanted to switch the apps installation path to the external sd card but did not succeed.
What am I doing wrong
I have not been able to root my springboard at all. It will go to a black screen that says enter fastboot and it just stays there. When I type to flash the recovery it says it cannot load it. I have adb and fastboot installed...could it be a driver issue? I now know that I am in the correct screen, just can't get this thing rooted. any help would be appreciated thanks.
Well I feel quite stupid. But figured out where I went wrong and for the love of God got my Springboard rooted. *whew*
Hi guys
I've tried everything, i bought this watch today and i was so hyped about it.
I tried to update it to 6.0.1 using adb on my mac.
The problem is when i do this command "adb reboot recovery" and then "adb devices" it shows no devices! (before entering recovery it actually shows the device in the list!
This is so wierd and there is absolutely no solution that worksfor me... anyone has any ideas?
Edit: The problem more clearly:
Ok guys so the problem was that my LG G Watch (square) for some unknown reason wasn't available in recovery mode through adb, that means when i would use the command "adb devices" in recovery mode, i would see the empty list without any devices, while anywhere outside the recovery (system, fastboot etc) i was able to communicate with the device. (Since i was so frustrated i didn't make it clear enough in the original post ) And my watch was on 4.4! ( :| )
The solution:
Ok, so the problem was the watch, because i tried a OS X (and a windows on the same mac) and 2 windows laptops, all with drivers installed (and done the "update driver..." stuff on all) and the problem still persisted.
This solution is for people whose device is not displayed while in the recovery mode in cmd/terminal.
This is what i did: (i didn't do this in the order because i literally tried every solution on the internet! but this is the order that i was finally able to solve the problem with.)
1. I downloaded this tool from this topic (go to the link, click on LG G Watch > G watch script tool > LG G Watch Restore Tools V9.8.zip)
2. Run this bat (i used a windows but it works on the mac too) 1 LG G Watch Tools for Windows.bat
3. Let it recognize the device
4. When the blue list comes up choose 4 ( you should be in bootloader)[cmd > adb reboot bootloader] when it's done, your device should be on 5.1.1.
5. Download this tool from this topic
6. In cmd/terminal type "adb reboot bootloader" then type "fastboot flash recovery [draggedfile] and drag the downloaded .img to the cmd and press enter.
7. Now you have installed a custom recovery called CWM
8. In cmd type "fastboot reboot" then after reboot "adb reboot recovery"
9. Now inside this tool swip down to "install ..." and swip (to right i guess) and stay here on the watch.
10. Now in cmd type "adb push -p [draggedfile] /sdcard/0/Download" and drag the 6.0.1 OTA update and press enter
11. Now the update is in your device as a zip file in this path : /sdcard/0/Download (it didn't work when i wanted to push it to "/sdcard" folder so i had to go deeper)
12. Now swip on install from sdcard and navigate to the path and choose the zip file.
13. Done! you have successfully updated your device without going into recovery mode!
Thank you very much @lfom for sticking to this topic and helping out in the process!
I just tried it with windows as well and ain't working... im so frustrated...
There's a guide in General section that you may want to read:
http://forum.xda-developers.com/g-watch/general/guide-how-to-fix-6-0-1-adb-bug-t3347122
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
miladkalbasi said:
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
Click to expand...
Click to collapse
So you are on 4.4 and want to update? What else? Rooted and custom recovery?
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
lfom said:
So you are on 4.4 and want to update?
Click to expand...
Click to collapse
Yes, i bought this watch yesterday and it's on 4.4 and i want to update to 6.0.1 (or any newer update)
lfom said:
What else?
Click to expand...
Click to collapse
I have never had developer experience with any android device before so i learned everything in like 6-7 hours, therefore there is a high probability that i might have made mistakes in the way but here's what i have done so far:
1. i tried to update the watch from "About" on the watch itself but kept getting "Something went wrong" error and couldn't fix it.
2. so i moved on to use my mac to do the update which took me 4-5 hours to figure out what SDK platform tools, ADB, OTA updates, bootloader, fastboot etc means.
3. i figured out all this and went on until i reached here: i have to use this commend in the terminal (it's like windows cmd): adb devices
so that i know my device is there and authorized on the companion android device (i see the device in the command shell), i then proceed to this command : adb reboot recovery , as soon as i type this command and press enter, the device reboots and enters recovery mode but it is also vanished from the system, by typing adb devices i no longer see it, i just see an empty list.
4. i also did unlock, wipe, restore back to stock ROMs (5.1.1 ROMS), tried TWRP (i then realized i can't do OTA updates with this tool)
5. i did all of these steps several times and always got the same results!
6. i also tried the windows on my mac and got the exact same results.
7. i tried 3 different windows laptops in the household (2 of which run win 8 and one runs win 7) but was not able to make it through installing the drivers (i couldn't see the android device when i clicked on update drivers...)
lfom said:
Rooted and custom recovery?
Click to expand...
Click to collapse
no i haven't rooted the device
lfom said:
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Thank you very much for your suggestion, i have already tried that and it doesn't actually give me any more options that i already have.
I've come to the believe that it's either my laptop (which only has 2 USB 3.0 ports and some people say it causes issues) or my watch. I have to try to use a different computer but i don't think i can access more computers or solve the driver problem on the 3 existing ones.
I really wish i could solve this by myself, i live in a country that i can't access warranty and stuff so i either have to fix it myself or get a professional's help.
i found this topic as well, that's exactly my problem.
I can communicate with the watch in bootloader and TWRP but not in the recovery mode (stock)
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
lfom said:
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
Click to expand...
Click to collapse
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
miladkalbasi said:
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
Click to expand...
Click to collapse
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
lfom said:
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
Click to expand...
Click to collapse
I solved the problem!
Funny thing is i didn’t see your answer and fixed it by myself but you actually proposed exactly what i had to do! Thank you very much for your effort and spending your time on this topic!
For others who might run into the same problem in the future I'm gonna update the first post and say what i did.
Cheers!
Hi,
For those who didn't receive the OTA by now and are on stock, non-rooted, here's the link : (rename to update.zip, update it via settings/update or update via recovery (update or adb sideload) etc.....)
Don't know if it'll work when on stock N-B06 (can't test it because i'm on custom ROM ). Otherwise downgrade to B05 again and upgrade to B08.
EDIT : For those where update.zip not show up (which is a common issue, don't panic, you can wait for the FULL update later on...) try :
1. rename to update.up or fota_B08_B12_ssl.up or A2017GV1.2.0B08.zip
2. try to update over recovery. Inthere try to adb sideload or update via SD
2a : ADB sideload : boot phone into recovery, setup ADB, put zip in ADB folder (you know...or drag it later on in terminal...), open terminal in ADB folder (shift+rightclick open terminal here), type adb devices (there has to be your "device-number" and recovery),on phone apply ADB update, then type command : adb sideload nameofyourzip.zip and enter. Done !
3. don't forget to try either on intSD or extSD
4. wipe cache in recovery and try again...
AFH link : https://androidfilehost.com/?fid=962021903579488106
updated in DownloadCenter : https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
don't just HIT&RUN....there's a :good: button for some reason
Hi,
my Device is on stock B05 and non-rooted. I've downloaded it. renamed und put it in to root of the internal Memory - still no Update found...
Same for me. I've tried place update.zip in internal storage and sd card but update not found.
Adb sideload works
I renamed the file to update.zip and put it on a microSD Card. Then installed over recovery. It worked. I was on original B05 before.
@jopomopo,
please tell the community how you did with sideload ADB. Thanks
dodo34 said:
I renamed the file to update.zip and put it on a microSD Card. Then installed over recovery. It worked. I was on original B05 before.
@jopomopo,
please tell the community how you did with sideload ADB. Thanks
Click to expand...
Click to collapse
I did that to but as always installation failed. What i did is to boot into recovery and choose there adb sideload. On your computer you send valid file with adb sideload update zip to the phone. Of course you have to have valid adb files installed on computer and know your way how to use power shell.
Can someone extract the modem of this rom and upload it here?
That would be really nice.
some new features spotted ?
Angelo_0 said:
some new features spotted ?
Click to expand...
Click to collapse
No new features. However, I have the impression that the fingerprint scanner is quicker. Anyone else?
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
no full rom?
how to enable VoLTE ?
MrMD69 said:
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
Click to expand...
Click to collapse
Same for me.
I needed to sideload the OTA (not an OTA anymore :silly.
And nothing relevant too in rom. It's enough for me anyway : security patch is already good to have.
Enjoy!
MrMD69 said:
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
Click to expand...
Click to collapse
Updated through ota (from b05). Indeed, things seem a bit faster. Most noticable for me is the fingerprint sensor.
Too early to confirm, but battery seems better than B05.
i think screen dpi a bit lower .so thats good
and ram performance noticable better
Hi
I am actually on B06, if I make a downgrade to B05 I loose all my data?
no .
Is there any TWRP version of this update available?
Upgraded to B08. Method:downgraded to B05 and then updated from recovery. Till now all is ok
Anyone got aboot from B05 (emmc_appsboot.mbn)? I am rooted stock. I restored untouched system and stock recovery but I get an aboot error on flash. I flashed aboot downgrade to B01 back in April to get fastboot back : https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
I'm not sure if this properly constitutes a soft-brick, but it's left me with an unusable OS at the least.
I was attempting to root my new honor 9 (STF-AL10) using TWRP and SuperSU, but TWRP had a permission denied error whilst flashing SuperSU (I forget the exact error :S). Since then I've spent 2 days just attempting to revert to stock, abandoning my root plans in despair.
My present situation is that I can boot into fastboot and flash recoveries OK, I can get into TWRP and stock recovery (whichever is flashed), and I can get into Android but with apps and features missing (such as the back and menu buttons!) I've tried many guides on flashing stock, but I either end up with an incomplete OS, or the stock recovery just says the update is incompatible. I'm at a loss with how to fix this at this point. Surely it is fixable given that I can get into fastboot and recovery? Does anyone have any similar experience, or advice on flashing stock from any state?
SOLVED
I managed to install a stock rom finally using the method here
The link to HWOTA.zip is broken, but I found it here
I had to fiddle with the HWOTA script a little to get it to work, in particular there is an typo:
Code:
$ADB shell "dd if=/tmp/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
should be
Code:
$ADB shell "dd if=/tmp/oeminfo.bin of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
I used this rom, and had to rebrand using HWOTA to STF-L09432.
After that the EMUI updater worked and installed the rom, and everything was fine. The only issue I've come across so far is that the updater seems to be missing, so I guess I'll have to manually update the rom in future. I was also able to re-flash TWRP and install SuperSU afterwards which was a bonus.
xionic334 said:
I managed to install a stock rom finally using the method here
The link to HWOTA.zip is broken, but I found it here
I had to fiddle with the HWOTA script a little to get it to work, in particular there is an typo:
Code:
$ADB shell "dd if=/tmp/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
should be
Code:
$ADB shell "dd if=/tmp/oeminfo.bin of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
I used this rom, and had to rebrand using HWOTA to STF-L09432.
After that the EMUI updater worked and installed the rom, and everything was fine. The only issue I've come across so far is that the updater seems to be missing, so I guess I'll have to manually update the rom in future. I was also able to re-flash TWRP and install SuperSU afterwards which was a bonus.
Click to expand...
Click to collapse
hi, buddy... iam here cause i have the same problem with you. but may be a little bit different. i got this gonna be suck when i tried to rebrand my model (stf-al10 into eu version). when installing oem the prosses was showing an error warning and incomplete action so i got a bootloop . so i tried again and again but at once i unintentionally choose "update" for the same model i had (not to rebrand). it was cool i taught, but when i check it, i got no updater and whatever you said in the thread.
i tried your recom, but all the links you put in are out. could you reupload again? thanks for your kindness
-sorry for my bad english-
thanks for replying.
EDIT: My solution was to have an exFAT formatted SD card with update.app, I had previously only tried on an ext4 formatted card.
Hi everyone!
I've been looking for days for a way to get my Honor 9 working again to no avail.
It started with me trying to install a custom ROM on my EMUI 5.1 Honor9, but when the touch buttons didn't work I decided to go back to stock. This is where the problems started.
FRP and bootloader was unlocked before doing this.
After many different firmware tries I managed to get into stock rom (B130), and apparently it locked FRP again, but since the touch buttons still didn't work I decided to rebrand with B120. Bad idea.
Now my phone has FRP locked, so I can't flash images from fastboot anymore (command not allowed), and no working OS.
I do however have TWRP installed as recovery2/e-recovery, so I can still adb push images and install them via TWRP.
I've looked through every thread on this forum and tried every possible solution I could find (extracting images from update.app, copying update.app to /dload on external sd, different firmware versions etc)
If there is there anyone here that is more experienced than me that can give me any pointers in the right direction, I'd be incredibly grateful!
As far i know there only 3 service repair firmwares publicly available which works the dload way. There nougat and are meant to use from nougat.
Alright, so they won't work for me no matter how hard I try?
What alternatives are left to me?
What's your region and version firmware actually ?
You stated you rebranded ?
What region region service repair firmware did you used ?
Region is EU, I'm not really sure what my original firmware is, but i suspect around B130? I know, I'm an idiot for not checking before I wiped it..
I tried at least, to install the B120 in order to get the capacitive buttons to work, but I'm pretty sure I didn't succeed.
I've been using EU firmware to try and get the phone up and runnin. A few different versions.
have you tried to flash again B130 whit 3 fingers mode?
mmmhhh but maybe you have need stock recevery....
With 3-finger mode you mean stock recovery? (Not twrp or stock eRecovery)
How would I flash this using stock recovery, via update.app method?
When flashing stock recovery to recovery partition it boots straight to twrp (flashed to recovery2) regardless of what buttons I hold. :/
If i flash twrp to recovery and stock eRecovery to recovery2 partition and restart holding vol+ and pwr, I get a screen similar to fastboot screen with "error 2 - could not load"
I'm afraid that if i flash stock both recovery and eRecovery, I have no way of flashing images or restore twrp due to FRP being locked...
Thank you everyone for taking the time to respond, really appreciate it!
not undestrand...
now you have TWRP installed or Stock recovery? phone turn on in system or have a loop? what it is the problem? only FRP blocked?
how you can falsh twrp and stock e-recovery if you have frp blocked?
what is happen when you turn on phone holding Volume + and Power Button WHITOUT ANY USB CABLE CONNECTED?
this is three fingers way:
1) download "stock service B130" from:
https://forum.xda-developers.com/hon...stock-t3696892
2) copy UPDATE.APP and update_STF-L09_hw_eu.app to external SDCARD into /dload folder
turn on the phone holding Volume + and volume - and power ( three fingers way)
if all is good, phone restart in stock recovery and update firmware....
you will have again bootloader and frp blocked after new firmware will be flashed
if you have a twrp installed you can try this method.... but i dont know if it work whit frp locked:
1) download "stock service B130" from:
https://forum.xda-developers.com/hon...stock-t3696892
2) download those 2 file from
https://mega.nz/#F!Y59nFYbJ!fb1f4UpEdgABZ4NhOfu1JQ
3) put all files in HWOTA7 directory on external SD
4)In TWRP find the folder HWOTA7 on the phone SD and from it flash the file "hwota7_update.zip"
he phone will reboot itself into the stock recovery and it will install the firmware.
++++++ Important ! ! ! ++++++
After have installed the firmware, you need to boot into the recovery and make a full Wipe
if all ok, b130 firmware will be flashed.
let me know if you try
First of all, thanks a lot for trying to help me!
I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:
#!/sbin/sh
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34
echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command
reboot recovery
Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.
These zip files do not exist in the B130 firmware you linked. What files should I use for this?
I tried running it anyway and got into recovery, however it says "Software install failed! The update package does not exist. Please download the package again."
Alright, that may have thoroughly f**d me. Now TWRP is replaced with stock eRecovery.
I suppose I can put files on the SD card by using my laptop, but then I'd need the correct files. Anyone?
Now you should be able to flash with b130 service Repair files:
http://androidhost.ru/v5
Instructions inside, you will need an sdcard formated to extfat.
I've tried SO many times trying to get this update method to work, but always stuck at 5%, until now!
Seems like exFAT is the key! When formatting the SD card on my laptop with linux, it became formatted as ext4, which was fine to read and write to in twrp, but however stock recovery seems to demand an exFAT partition.
Today I went out and bought an USB SD card reader and formatted with exFAT on my windows machine and lo and behold the update was installed!
I don't know if I'm an idiot for missing this fact or if it is not iterated enough. This solved my issue though!
Thanks a lot, Oslo83 and Angelobiz
miffeltoffel said:
First of all, thanks a lot for trying to help me!
I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:
#!/sbin/sh
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34
echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command
reboot recovery
Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.
These zip files do not exist in the B130 firmware you linked. What files should I use for this?
Click to expand...
Click to collapse
yes... you have right...i missed somethings:
update.zip same same
update_STF-L09_hw_eu.app have to rename in update_all_hw.zip
update_data_public.zip dont need for restore....
happy that you have solved.
which files have you used?
I used the stock B130 files in the thread that you posted, worked like a charm. As stated, the issue seems to have been that Linux cannot format in exFAT, and stock recovery can only read exFAT.