Hi,
Using the following commands i installed a custom recovery WTRP 3.2.2-0 in my TPLink Neffos X1 Lite
fastboot devices
fastboot oem unlock
fastboot flash recovery recovery.img
I didn't root my phone at this stage. I tried to restart but now I get the message "your device has been unlocked and can't be trusted. Your device will boot in 5 secords" and it returns back to WTRP.
So, why I can not boot normally? Do I have to lock the recovery partition with "fastboot oem lock" or will I brick my phone? If I lock it, can I unlock it again?
Inside TWRP recovery it reports that system partition is still unmodified, but trying to get a backup to the folder "/data" it reports "failed to mount '/data' (invalid argument). What seems to be wrong here?
Regards,
PS: Did I already lost my phone data apps and settings doing all those above?
*update.
I used the command "fastboot oem lock" and I get this warning.
lock bootloader ?
if you lock bootloader you need to install official operating system software in this phone.
To prevent unauthorizing access to your personal data, locking the bootloader will also delete all personal data from your phone (factory reset)
Press the Volume Up/Down buttons to select Yes or No.
I selected NO, but how it is supposed to continue work with my phone?
First of all, let me kindly give you a clear and firm warning: If you modify any partition (like the recovery), DO NOT UNDER ANY CIRCUMSTANCES relock the bootloader. What that would essentially be doing is telling the phone to only boot if unmodified and factory clean, when it's modified and obviously not clean. It will either fail to lock the device, or succeed and cause problems, which might include bricking.
You have almost 100% likely factory reset the data partition and deleted all your apps and data if you unlocked the device. This is because, as part of the unlock process, most devices erase all data and perform a factory reset as part of the procedure. Backing up before trying to do is is not only strongly advised, but pretty much a requirement. The reason the data partition can't be mounted is because it's either encrypted, or blank.
Now, as you to when you get the warning that the device is unlocked and will boot in 5 seconds, try this: Tap one of the volume or power buttons. briefly I find some devices hang until you do so. You know, just turn it on, and when the message appears, try tapping one of them and waiting 10 seconds or so, try the next one, etc.
I myself and just trying to figure out how to root a device of mine, so I'm not experienced.
Please wait for advice from others who are more knowledgeable before trying anything else.
TheNH813 said:
First of all, let me kindly give you a clear and firm warning: If you modify any partition (like the recovery), DO NOT UNDER ANY CIRCUMSTANCES relock the bootloader. What that would essentially be doing is telling the phone to only boot if unmodified and factory clean, when it's modified and obviously not clean. It will either fail to lock the device, or succeed and cause problems, which might include bricking.
You have almost 100% likely factory reset the data partition and deleted all your apps and data if you unlocked the device. This is because, as part of the unlock process, most devices erase all data and perform a factory reset as part of the procedure. Backing up before trying to do is is not only strongly advised, but pretty much a requirement. The reason the data partition can't be mounted is because it's either encrypted, or blank.
Now, as you to when you get the warning that the device is unlocked and will boot in 5 seconds, try this: Tap one of the volume or power buttons. briefly I find some devices hang until you do so. You know, just turn it on, and when the message appears, try tapping one of them and waiting 10 seconds or so, try the next one, etc.
I myself and just trying to figure out how to root a device of mine, so I'm not experienced.
Please wait for advice from others who are more knowledgeable before trying anything else.
Click to expand...
Click to collapse
It always returns to the TWRP no matter what. I downloaded the official firmware ~1.5GB but I don't know how to apply it.
I want to reset anything to factory defaults, is that possible? I found also a tool called SP_Flash_Tool to apply this firmware but I really have a hard time to understand how it works.
Related
Please help a noob dad with a distraught teenage son who is not as tech savvy as his peers, or his noob dad.
Son and I both have absolutely stock TMo HTC Ones. Mine is fine.
His had all his music on it, and his music was not backed up. (His laptop's hard drive crashed just two weeks ago and he had not gotten around to restoring his music yet. He is not having a good month with tech.)
His phone without warning entered a boot loop. It restarted itself, reached the bootloader/simply brilliant splash page, reached the T Mobile LTE splash page, reached the HTC One Beats Audio splash page, dimmed a bit, went blank, and then restarted the boot sequence. This goes on infinitum, and even after we let the phone battery run down to zero, recharged and started it again.
We can enter the bootloader by pressing volume down and the power key at the point where the screen goes blank after the HTC One Beats Audio splash, and from there we can go to recovery or into fastboot. When in fastboot, the phone can be connected to a computer, where it shows up as an "unspecified" device called Android 1.0. This device does not show up as a storage device - so we don't see the files. It has a driver called MyHTC. The phone screen shows FASTBOOT USB in red, but running adb with the command adb devices doesn't show anything in the device list.
As I said, the phone is absolutely stock - that means it is locked, and never was unlocked. And I understand that unlocking the bootloader to install a custom recovery would wipe the data files, thus defeating the purpose of the exercise.
We won't mind trying a factory reset, or even trying to root the phone, if we can first get to the music and save it. Is there some way to save it?
Now, mind you, two days ago terms like adb, bootloader, Android SDK, custom recovery, etc., were completely foreign to me. These are things I have picked up trying to solve the problem with Google and personal grit. So please bear that in mind when answering.
Is there some way to access the data files on this phone from the bootloader screen or from the recovery screen? If the phone can't be booted up and the phone can't be unlocked without being wiped clean, it seems my son is going to be spending a lot of time and money recreating his music library. Is this true? Have we finally found a situation that Dad can't rescue his offspring from?
Thanks in advance for any ideas...
GenerousDad said:
Please help a noob dad with a distraught teenage son who is not as tech savvy as his peers, or his noob dad.
Son and I both have absolutely stock TMo HTC Ones. Mine is fine.
His had all his music on it, and his music was not backed up. (His laptop's hard drive crashed just two weeks ago and he had not gotten around to restoring his music yet. He is not having a good month with tech.)
His phone without warning entered a boot loop. It restarted itself, reached the bootloader/simply brilliant splash page, reached the T Mobile LTE splash page, reached the HTC One Beats Audio splash page, dimmed a bit, went blank, and then restarted the boot sequence. This goes on infinitum, and even after we let the phone battery run down to zero, recharged and started it again.
We can enter the bootloader by pressing volume down and the power key at the point where the screen goes blank after the HTC One Beats Audio splash, and from there we can go to recovery or into fastboot. When in fastboot, the phone can be connected to a computer, where it shows up as an "unspecified" device called Android 1.0. This device does not show up as a storage device - so we don't see the files. It has a driver called MyHTC. The phone screen shows FASTBOOT USB in red, but running adb with the command adb devices doesn't show anything in the device list.
As I said, the phone is absolutely stock - that means it is locked, and never was unlocked. And I understand that unlocking the bootloader to install a custom recovery would wipe the data files, thus defeating the purpose of the exercise.
We won't mind trying a factory reset, or even trying to root the phone, if we can first get to the music and save it. Is there some way to save it?
Now, mind you, two days ago terms like adb, bootloader, Android SDK, custom recovery, etc., were completely foreign to me. These are things I have picked up trying to solve the problem with Google and personal grit. So please bear that in mind when answering.
Is there some way to access the data files on this phone from the bootloader screen or from the recovery screen? If the phone can't be booted up and the phone can't be unlocked without being wiped clean, it seems my son is going to be spending a lot of time and money recreating his music library. Is this true? Have we finally found a situation that Dad can't rescue his offspring from?
Thanks in advance for any ideas...
Click to expand...
Click to collapse
Very well written question... I'd start with a Fastboot command (entered while the phone is connected to pc and phone screen shows fastboot usb) 'fastboot erase cache.' It will return success, failure, or waiting for device. If it returns success enter 'fastboot reboot.' There is a small possibility this will allow his phone to boot normally.
You are correct that unlocking the boatloader erases the phone although there may be alternative if s-off is possible while the bootloader is locked - anyone? And ADB commands only work when the phone is booted into android or recovery not fastboot. And I have no experience with stock recovery but it might be possible to wipe cache there too.
Sent from my HTC One using Tapatalk
Thanks very much for the reply.
I tried the command 'fastboot erase cache' and it replied with "******* Did you mean to fastboot format this partition?"
Then, without waiting for an answer to that question, it proceeded - it said "erasing cache" and then "OK [0.575s]" and then "finished. Total time 0.575s."
I interpreted that as success, so I proceeded to enter the command "fastboot reboot." The phone rebooted - into the same boot loop I described earlier.
If you (or anyone) thinks that adb will help, I CAN get the phone into recovery mode as well. The phone allows me the option to wipe the cache partition from there (which I did), but a friend of mine (actually, my ophthalmologist as well) suggested I wipe the dalvik cache. Not only do I not know what a dalvik cache is, but I don't see any option for it on the HTC One recovery menu. I also don't know whether wiping the cache partition from the recovery menu is any different than what I did with the fastboot command - but in either event neither one eliminated the boot loop.
Any more ideas for either getting the phone to boot or saving the music so we can factory reset and then restore the music would be appreciated!
make a full adb backup and then unpack the contents
http://androidforums.com/application-development/163138-how-basic-adb-commands.html
http://forum.xda-developers.com/showthread.php?t=1572600
holmesnmanny said:
make a full adb backup and then unpack the contents
http://androidforums.com/application-development/163138-how-basic-adb-commands.html
http://forum.xda-developers.com/showthread.php?t=1572600
Click to expand...
Click to collapse
The only abd access he'll have at this point is for sideloading (Does the stock recovery even do sideload?), which if I am not mistaken, allows only a small subset of abd access (not enough to do the backup).
Would be so much easier if the handset was unlocked. A custom recovery would go a long way to recovering any data from the device... I've never had a device I didn't unlock right away so I'm afraid I can't help much beyond giving my doubts regarding the adb solution...
PhoenixPath said:
The only abd access he'll have at this point is for sideloading (Does the stock recovery even do sideload?), which if I am not mistaken, allows only a small subset of abd access (not enough to do the backup).
Would be so much easier if the handset was unlocked. A custom recovery would go a long way to recovering any data from the device... I've never had a device I didn't unlock right away so I'm afraid I can't help much beyond giving my doubts regarding the adb solution...
Click to expand...
Click to collapse
PhoenixPath, I'm afraid, was right, and we ended up doing a factory reset. My son restored the phone's contents as best he could, making sure to back up this time, and then powered off, but when powering back on the PIN unlock keyboard doesn't come up.
Sigh.
Any ideas? I'll post another thread on this...
Thanks to all who offered ideas.
Did you even try to do what I said or did you just assume I was wrong in full ?
I guess if you're not really interesting in ideas I guess you'll just choose altogether not to try some.
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.
Many of us are on custom OS and want to return back to stock Indian OS which was not possible till now. Below posted is a tried and tested method by me as well as my friend @ankan1993.
I assume you are unlocked BL and your device is atleast not bricked.
Please follow this guide step by step to get a stock working device. This is for Honor V10 Indian Version C675 and I'm not responsible for your loss if you make this worst by trying this on other variants/models or if you choose not to follow this guide properly.
I assume you are on Berkley TWRP with the latest version, unmodified one.
Downloads : (Keep both in your fastboot folder in PC)
Stock Recovery : https://drive.google.com/file/d/1WEUHRrba1dV3109e7h7b3Hp_aJhy0vM8/view?usp=sharing (stockrec.img)
Stock System Image : https://drive.google.com/file/d/1IABtk7HJ9ml6kOpytYHrnT6z3C1_9IfW/view
1. Enter TWRP and go to wipe -> Advanced -> Select system and data, and wipe them.
2. In TWRP, go back and Click Reboot button on main screen and reboot to Bootloader.
3. Connect you device and open cmd_here (open as administrator) from fastboot folder. ( I assume fastboot is installed and working in your system. You can check by the command "fastboot devices" . Device should show there. )
4. Type "fastboot flash recovery_ramdisk stockrec.img" (It should complete without error)
5. Once completes, Type "fastboot flash system system.img" (This may show error like "Invalid sparse file format". Ignore that and keep waiting for 10-12 minutes until the system gets flashed completely.)
6. Once it gets completed, disconnect your device and then press Vol up + power, until it screen shows stock recovery.
7. In stock recovery, use factory reset and cache wipe option one by one and then reboot.
Hit thanks if you think it helped :fingers-crossed:
Finally, after days, after being tormented by the bugs of custom Roms we have something to cheer about. Kudos Oreopie! Cheers to the long hours.
Kudo's bro.. appreciate your efforts :good:
Will this method also lock the Bootloader to stock?
vardaraju said:
Will this method also lock the Bootloader to stock?
Click to expand...
Click to collapse
No, It won't.
Im unable to access bootloader/recovery mode after unlocking bootloader with volume down+power button, used twrp option to reboot to bootloader, but now i flashed stock recovery and this system image, device bootlooped and im unable to access bootloader, i hold the keys but instantly that warning screen comes up, please help..started using android since 2010 with HTC desire HD and never in my life i stepped in service center because those devices were brick proof, looks like honor made me step into service center
didnt work for me, followed exact steps as mentioned above but stock recovery keeps giving error while factory resetting the device, device ends up in bootloop,, this device is crazy, i need to connect my device to pc and then press voldown+ power to access bootloader else it just jumps to warning screen
aditya desai said:
didnt work for me, followed exact steps as mentioned above but stock recovery keeps giving error while factory resetting the device, device ends up in bootloop,, this device is crazy, i need to connect my device to pc and then press voldown+ power to access bootloader else it just jumps to warning screen
Click to expand...
Click to collapse
Obviously warning screen will come up, but at the same moment you have to just leave power button and keep on pressing vol down button, until you get into bootloader mode. It takes time bro and let me tell you one thing, no matter which mode you boot, no matter what ROM it is, once the bootloader is unlocked it implies that the unlocked warning screen will show and then it will be allowed to get into whatever mode you wish.
Try it as I told, be patient and follow the same guide exactly if you do not wish to visit service centre. There is nothing wrong happening with you other than an improper method being followed in haste
aditya desai said:
Im unable to access bootloader/recovery mode after unlocking bootloader with volume down+power button, used twrp option to reboot to bootloader, but now i flashed stock recovery and this system image, device bootlooped and im unable to access bootloader, i hold the keys but instantly that warning screen comes up, please help..started using android since 2010 with HTC desire HD and never in my life i stepped in service center because those devices were brick proof, looks like honor made me step into service center
Click to expand...
Click to collapse
In cases of a bootloop, follow this- https://forum.xda-developers.com/ho...ustom-rom-to-stock-rom-honor-view-10-t3802872
will the system image work on honor 7x??
Can you share the screenshot of the about phone screen please
Anyone got it working? the stock recovery keeps showing error when factory resetting the device, error shows some where at 12%, it just shows exclamation mark, ROM doesn't boots up
Not working!
Rj_Param said:
Not working!
Click to expand...
Click to collapse
What is the issue and what you want to do.
shashank1320 said:
What is the issue and what you want to do.
Click to expand...
Click to collapse
I am on lineage and want to go back to the stock ROM. I also have backup of my system but i have tried many times after flashing the system image it is going in boot loop so i have followed all methods and it's not working..
Every time i have tried after flashing system whenever i go to recover to do factory reset it failed. Even i tried to lock the bootloader but nothing seems to be working.
Rj_Param said:
I am on lineage and want to go back to the stock ROM. I also have backup of my system but i have tried many times after flashing the system image it is going in boot loop so i have followed all methods and it's not working..
Every time i have tried after flashing system whenever i go to recover to do factory reset it failed. Even i tried to lock the bootloader but nothing seems to be working.
Click to expand...
Click to collapse
Because on custom you are on 8.1 and twrp doesn't support yet.
May be you can try dload the b161 version which is out on firmware finder now.
shashank1320 said:
Because on custom you are on 8.1 and twrp doesn't support yet.
May be you can try dload the b161 version which is out on firmware finder now.
Click to expand...
Click to collapse
I'll give it a try today...thanks
Invalid
as you mentioned, i m getting this error "invalid sprase file format". I waited more than 30 mins, still i couldn't see any message like compeleted or success. Still showing only that error "invalid spase file format". Help me with this.
Tamilarasan_Indian said:
as you mentioned, i m getting this error "invalid sprase file format". I waited more than 30 mins, still i couldn't see any message like compeleted or success. Still showing only that error "invalid spase file format". Help me with this.
Click to expand...
Click to collapse
Invalid sparse error happens when trying to flash .IMG files in Windows system.
It can be easily solved by using Linux system.
thanks for the reply
miststudent2011 said:
Invalid sparse error happens when trying to flash .IMG files in Windows system.
It can be easily solved by using Linux system.
Click to expand...
Click to collapse
I dont have Linux , and tried to flash other SYSTEM.img file for honor v10 from other threads. It completed flashing but still am not able to login into phone successfully. Still stuck at bootloop. Help me