[Q] Lenovo A2107A-H Help with restoring to OE ROM - Android Q&A, Help & Troubleshooting

Hello,
I am reaching out one last time to see if I can get my tablet back to the way it was, before I messed it up doing the CWM install. I am going to put as much information on what I have done and be as clear as I can.
I am trying to avoid sending it in to Lenovo and try for a warranty, or paying $50 deductable to AT&T for my Full Protection Plan I am paying for each month on this FREE tablet I got from a promotion.
My device Info:
Lenovo IdeaTab A2107A-H on AT&T purchased at AT&T, Rooted with CWM Touch, European Stock Rom.
First thing I did was root using this thread, method 1 with 4.03root. This worked fine. I tried several times to Backup and install CWM with this method using MobileUncle. I even tried the “updates” that were posted there. Now, there is only one use to be three or four.
Second, I followed this on another site through a Google search to make a scatter-text and a back-up on my PC. This part of my problem now as I did not realize the back-up did not do a complete back-up of the tablet as I thought. It skipped some important files, “ANDROID” and “NVRAM” .
Third, I posted on the thread in the first link for help because I could not get CWM on no matter what I tried, and ursulavasey was nice enough to email me some programs and instructions. Using pemergency’s thread here. Which formats the tablet to install CWM
.
My major problem is, with the custom ROMs I have tried, FoxTrot, Tesmart, and the European Stock from here. It will not connect to the AT&T Network correctly. I can reset the IMEI number and connect but, it will drop out a lot and will not run on 3G. Except the Euro Stock, it says 3G in the notification area, it just seems slower than the OE Rom. I also downloaded a Stock Rom that was in two zip files and not sure how to get them into one file to flash, can’t find the link for that one though.
Just for fun I re-followed the GSM Hosting scatter-text thing again with my wife’s tablet and got a better back-up. Everything worked great, However when I flashed it to mine it will not let me reset the IMEI number with DroidTools.
So basically… Is there a way to fix this and put the OE Stock AT&T Rom back on somehow? or Can I re-write something in the back-up from my wife’s to get it to take my IMEI?
Sorry this is long, I wanted to get as much info in the OP as I could. Thank You for your time, ANY help would be appreciated. I hope I put this in the correct section, If not I apologize.

SOLVED! Except one small thing.
Well, I managed after trial and error to merge my incomplete back-up with the complete back-up of my wifes tablet. I used all the files from mine, added in her "Android" folder and CWM, formated and flashed with SPFlash Tool. At first the tablet would not boot to the OS, it would boot into CMW. So I tried a "Factory Reset" from there, and rebooted and successfully got the OS up. Then I could Root it again, replace IMEI number and setup the tablet again.
The only small thing I can not seem to make go away is the "NVRAM WARNING: Err = 0x10" in the Wifi Settings. I have tried several methods to make this go away. Nothing so far worked permently, only until a reboot or a screen unlock. I did not get this when I flashed my merged back-up using the "stock recovery" instead of CWM, so I think it is that recovery.
What is this "NVRAM WARNING: Err = 0x10" anyway and is it a major or minor problem?
I can't remember exactly what methods I tried, Is ther one that works 100%?

Related

[Q] Very odd problem related to efs

Update:
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
Click to expand...
Click to collapse
So yesterday I got the odd 'Encryption Unsuccessful' error (phone only boots into screen saying: Encryption Unsuccessful, you have to reset...) after my phone ran mysteriously low on battery, rebooting, everything crashing, pulling out the battery and rebooting again.
I did a factory reset/data wipe from within CWM, and the phone would boot up normally, but I got no cell service. I checked in settings, and the baseband was listed as 'Unknown' as well as the IMEI. I had a look in the /efs folder and it was empty except for two more empty folders, 'bluetooth' and 'wifi'.
My problem now is that regardless of what I add or remove to /efs, or if I restore it from a backup, it always resets itself after boot to just contain those two empty folders 'bluetooth' and 'wifi', and the baseband and IMEI are still unknown.
Any help would be much appreciated!
AUAnonymous said:
So yesterday I got the odd 'Encryption Unsuccessful' error (phone only boots into screen saying: Encryption Unsuccessful, you have to reset...) after my phone ran mysteriously low on battery, rebooting, everything crashing, pulling out the battery and rebooting again.
I did a factory reset/data wipe from within CWM, and the phone would boot up normally, but I got no cell service. I checked in settings, and the baseband was listed as 'Unknown' as well as the IMEI. I had a look in the /efs folder and it was empty except for two more empty folders, 'bluetooth' and 'wifi'.
My problem now is that regardless of what I add or remove to /efs, or if I restore it from a backup, it always resets itself after boot to just contain those two empty folders 'bluetooth' and 'wifi', and the baseband and IMEI are still unknown.
Any help would be much appreciated!
Click to expand...
Click to collapse
[GUIDE] Recover your IMEI in 9 steps.
(Found in the General section via a Google search...)
ctomgee said:
[GUIDE] Recover your IMEI in 9 steps.
(Found in the General section via a Google search...)
Click to expand...
Click to collapse
Oh sorry I should have mentioned I've tried that as well as many other efs recovery tools. I can't follow that guide because step 4 is "go to EFS folder using root explorer, and delete 'nv_data.bin', 'nv_data.bin.md5'", but there are no such files automatically generated like it says. Thanks though.
AUAnonymous said:
Oh sorry I should have mentioned I've tried that as well as many other efs recovery tools. I can't follow that guide because step 4 is "go to EFS folder using root explorer, and delete 'nv_data.bin', 'nv_data.bin.md5'", but there are no such files automatically generated like it says. Thanks though.
Click to expand...
Click to collapse
Did you read the whole thread? Specifically, check out pages 5 & 6.
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
AUAnonymous said:
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
Click to expand...
Click to collapse
Nothing you say here convinces me you read what I had to say, and actually read those pages. Because they would have led you to tools you don't mention, that could have helped you.
ctomgee said:
Nothing you say here convinces me you read what I had to say, and actually read those pages. Because they would have led you to tools you don't mention, that could have helped you.
Click to expand...
Click to collapse
Trust me I've tried using GSII_Repair, HC-k Tool, EFS Pro, reformatting 'mmcblk0p1' via adb and via an on the phone terminal emulator and doing a bunch of other stuff, and while I really do appreciate your help (no one else has even suggested anything , and it's understandable that you're probably used to dealing with idiots, 11 year olds and people that barely speak English), it seems like my problem goes deeper than simply the efs folder being messed up somehow (which I think the original "Encryption Unsuccessful" error points to as well). At any rate, the problem now is not being able to flash a ROM using Odin, and the more I try the more I'm thinking that I'm basically screwed. And before you ask, I've gone through a lot of this thread already, as well as tried other random purported solutions, but any suggestions are definitely welcome.
AUAnonymous said:
Trust me I've tried using GSII_Repair, HC-k Tool, EFS Pro, reformatting 'mmcblk0p1' via adb and via an on the phone terminal emulator and doing a bunch of other stuff, and while I really do appreciate your help (no one else has even suggested anything , and it's understandable that you're probably used to dealing with idiots, 11 year olds and people that barely speak English), it seems like my problem goes deeper than simply the efs folder being messed up somehow (which I think the original "Encryption Unsuccessful" error points to as well). At any rate, the problem now is not being able to flash a ROM using Odin, and the more I try the more I'm thinking that I'm basically screwed. And before you ask, I've gone through a lot of this thread already, as well as tried other random purported solutions, but any suggestions are definitely welcome.
Click to expand...
Click to collapse
Yeah, sorry. Unfortunately, for the most part, I do find myself dealing with the group you describe.
Well if you've done the "fix unflashable" thread already... Hmm. I don't know then. When you say you're not able to flash, what do you mean, exactly?
ctomgee said:
Yeah, sorry. Unfortunately, for the most part, I do find myself dealing with the group you describe.
Well if you've done the "fix unflashable" thread already... Hmm. I don't know then. When you say you're not able to flash, what do you mean, exactly?
Click to expand...
Click to collapse
Well everything is fine in Odin until it gets to "NAND write start", which it never gets past (I've left it overnight). I've tried different ROMs, repartitioning, a different USB cable and everything else I could think of but I've really given up all hope now .
If it keeps failing at NAND write, NAND is stuffed. Service centre job. JTAG repair won't fix it & a person who normally does JTAGs won't be able to fix it at all unless they're able to swap out the NAND.
Well thanks for the confirmation at least :/ looks like I might be getting the GSIII seeing as I can get it on contract at the discounted price. The only downside being that I'll have to get a limited data plan and that the $700 I spent on this one go down the drain unless I can repair it...
AUAnonymous said:
Well everything is fine in Odin until it gets to "NAND write start", which it never gets past (I've left it overnight). I've tried different ROMs, repartitioning, a different USB cable and everything else I could think of but I've really given up all hope now .
Click to expand...
Click to collapse
Hi, I had a similar problem with not being able to write a kernel, and ending up with the logo and thebn black screen.
The way I fixed it was to use the Recovery Mode to reflash the rom that I had last working. (in my case it was wannamlites stock ICS). After that I was able to then flash back to my previous Gingerbread Custom rom using CWM's restore function.
Q) You didn't happen to use CWM Touch recovery did you?
*** there is a known issue with CWM touch recovery (which is built on an ICS base) and certain emmc (internal sdcard) firmware id
which could result in the flash being corrupted in a way that can't be fixed outside of the factory.
See http://forum.xda-developers.com/showthread.php?t=1648362
By the way, if your phone does boot, can you dial *#1234# and tell me what the H/W is reported as. Mine currently says "unknown"
centuriondan said:
Hi, I had a similar problem with not being able to write a kernel, and ending up with the logo and thebn black screen.
The way I fixed it was to use the Recovery Mode to reflash the rom that I had last working. (in my case it was wannamlites stock ICS). After that I was able to then flash back to my previous Gingerbread Custom rom using CWM's restore function.
Q) You didn't happen to use CWM Touch recovery did you?
*** there is a known issue with CWM touch recovery (which is built on an ICS base) and certain emmc (internal sdcard) firmware id
which could result in the flash being corrupted in a way that can't be fixed outside of the factory.
See http://forum.xda-developers.com/showthread.php?t=1648362
By the way, if your phone does boot, can you dial *#1234# and tell me what the H/W is reported as. Mine currently says "unknown"
Click to expand...
Click to collapse
Thanks for the advice but unfortunately I can't boot into recovery, only download mode., and I wasn't using CWM touch beforehand. It didn't even break when I was flashing a ROM, just when I was using the phone normally. I'm going to be in Europe in a couple weeks and I'll be able to take it in to a repair center where it's still under warranty. All I need to do is to use a USB Jig to reset the counter back to 0 so they'll work on it.
Have you tried Heimdall:
And I'd suggest reinstalling CM9. I found that when I had issues re-installing the kernel that I had to go back to the last working rom (ICS based) b4 I could downgrade.
The fact that you can't get into recovery indicates that either the primary or secondary bootloader is corrupted. Try flashing them again with the CM9 versions. Use the USB jig to get into download mode everytime you do flashing so that if you trash it further the counter is always zero. Also use the original USB cable with no hubs in between the phone and computer, and remove any other usb devices plugged in too.
BTW What was the result of *#1234* HW version?
i've read through all the posts from this topic. mine situation is slightly different.
I"m able to flash to any ROM. I can jump from gingerbread to ICS or vice versa with Odin.
When i type *#06#, it always show "unknown imei" no matter which firmware i'm on.
when i checked in EFS folder, i only have 2 folders : bluetooth and wifi.
I've tried to copy EFS files from people from this forum and paste into the phone's EFS. As soon as i restart the phone, back to 2 folders in its again.
any solution?
aznboix said:
i've read through all the posts from this topic. mine situation is slightly different.
I"m able to flash to any ROM. I can jump from gingerbread to ICS or vice versa with Odin.
When i type *#06#, it always show "unknown imei" no matter which firmware i'm on.
when i checked in EFS folder, i only have 2 folders : bluetooth and wifi.
I've tried to copy EFS files from people from this forum and paste into the phone's EFS. As soon as i restart the phone, back to 2 folders in its again.
any solution?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17587351, but I see you claim to have tried this already. If it didn't work, you'll need to take it to service.
BTW, the efs folder from another phone won't help you. IMEI is unique to each phone.
i dont have any files in EFS excepte the two folders that i mentioned above. Can't even start the procedures.
Service centre job, or contact Odia via PM & he might be able to recover it for you (for the cost of a case of beer).

[Q] help a noob, efs folder vanished, failed to mount. tried many things

Hi guys, firstly I'd just like to say I have followed all the protocol that is required on here and been reading and researching/ applying fixes for the past few days now. I have tried to help myself as far as i possibly can but i am still having no luck and i don't think too many people have had the exact similar issue after reading all the other threads that are similar to my issue.
with some of the fixes it is my first time using them as i have never needed to in the past, so bare with me if my level of understanding isn't as great in some departments.
Now onto the issue:
I own a galaxy s3 i9300 and it has been rooted on stock rom since day 1 about a year ago. A few days ago my phone battery died, and when connnected to the charger it had this grey icon with a circle. It wouldn't boot up either so after searching on the net i thought i would listen to the advice of clearing the cache etc etc but this didn't work and neither did the wipe data/dalvik in CWM.
So i reflashed a stock jellybean rom and it worked fine.
It was then at this stage i thought i might as well upgade to a custom rom as every galaxy i had owned before i had done it on, and my current Note tablet is also running custom rom.
I first loaded a stock 4.3 rom and then flashed the slimbean 4.3 with gapps ...and it worked perfectly. I found a couple of issues with the browser which i use a lot so i downgraded to a 4.2.2 version of slimbean with gapps and this made the browser really fast again and all was perfect.
I had been using this for two days or so and everything was smooth, including charging etc until one night it had that same grey battery icon again with the circle and would get stuck booting at the samsung logo.
So as this had happened before i thought i would just flash a stock rom....this is where it all started going mad
Bearing in mind, every flash i always did it properly and wiped cache/dalvik cache and wiped data three times for each one just to make sure as i didnt have anything of value so wanted a fresh wipe each time and didnt need to back anything up.
now before i get flamed i realise i made a huge stupid error in not backing up my efs folder before hand as i had done with every previous phone but because i was under pressure to get it working it skipped my mind totally.
So i flashed a stock jellybean 4.2.2 rom and still bootloop with the EFS not found invalid argument error
i flashed a 4.3
i flashed a 4.1
i flashed a different 4.1
i flashed a different 4.2
i tried loads but nothing worked
so after reading that this would not help as it doesnt touch the efs i looked into fixes that others had done
i tried to follow this http://forum.xda-developers.com/showthread.php?t=2197515
So i downloaded efs professional / adb tool
i downloaded busybox
and cwm was already on the phone but i downloaded philz cm incase i needed that too
now as the phone doesn't turn boot up i can't access anything, i can only access download mode and CWM.
When i open efs professional it says current device offline, turn on allow usb debugging to confirm your phones RSA fingerprint and click ok.
I have no idea what to do about that because i can't get into the phone.
Regarding busybox i have no idea how to get that to install on the phone, i have tried writing some stuff to push it in the adb shell (but because its my first time using adb shell and command prompt i have no idea if i am doing it correctly). Can you install it with odin?
also regarding adb shell i followed the guide http://forum.xda-developers.com/showthread.php?t=2197515 and got into [email protected] and SU....and then when on the phone in cwm i clicked mount efs...and obviously it failed. I went into the log as said and /dev/block/mmcblk0p3 was the file it failed to mount
the thing is everything after that step doesnt work, as i can't create an image of mmcblk0p3 as it says it can't find it as if it doesnt exist.
So im screwed as it effectively is saying i don't even have that file or efs folder i think?
The thing is i never had any issue with losing imei or anything like that at all and this just happpened out of the blue without me doing anything as such
any ideas?.....would be HUGELY appreciative for anyone willing to take the time out and help me with this as i'm not sure i can explore any more avenues on my own with my limited knowledge and at the same time don't want to give up.
PS. I also have access to a galaxy s3 i9305 ....and can possibly try and source another i9300 from a family member IF this helps in any way or makes life easier?
Stickied faqs and guides .
No IME/ EFS
service centre repair is your best choice if you have read and tried the stickied fixes .
Reads like efs partition corrupted and your phone was already suffering with nand memory issues.
There is no substitute for an efs backup, you cannot recreate the unique information it contained.
Take it to a reputable repair centre, they will be able to get it back to normal, but you are still left with why it keeps corrupting -which may require a new motherboard.
Sent from my GT-I9300 using Tapatalk
Mod Edit
Please refer to ,and post in the stickies in the General section.
Thread closed
malybru
Forum Moderator

[Q] I9100G IMEI and Basemand version unknown

Hello all,
I tried to stop myself from creating an user and also from starting a new thread on XDA, but i find myself in a bit of a huge mess.
I have a Galaxy S2 I9100G. I find it is an awesome phone, sadly not in the state i have it right now.
I have flashed a CM 10 ROM on it.
All i did is install a modified zImage that had a CWM in it using Heimdall. (It went well)
I have then made a quick backup using CWM and then flashed the CM 10 zip yet again using CWM.
I have then installed an Omni rom using the same flashing with CWM method.
This also went well.
I had to revert to CM10 cause i disliked the Omni rom. After some time (a week or so) i had to revert to the backup cause there was some data i needed, that i had saved in a note created on the stock rom. (This also went well)
After the data was saved i went back to CM10. (This also went flawlessly).
After a while (a few days) i cleaned my phone a bit. After assembling it and starting it up, the signal was gone. At first i was thinking that it is the place i liv in. This sometimes happens where i live. After a while, i came to see that there was no signal nomater where i was. I dissasembled the phone, thinking i might have done a mistake in connecting something back, all was connected back well and the phone still did not have signal. I came to see after playing around with the options that i have had no IMEI and no Baseband version.
What i tried was the following:
Booted to recovery:
in CWM i immediately flashed the created recovery. I have had no IMEI and baseband.
I then found some forums describing the deletion of the nv_data.bin+nv_data.bin.md5 files and renaming the .nv_data.bak to nv_data.bin and letting the md5 being created for it.
I deleted the data from /efs and then let the phone recreate the whole thing from scratch, all i did more was to copy the IMEI and .nv_data.bak file which i renamed to nv_data.bin
I then tried to flash the /efc with a zip file in CWM still to no avail.
I then tried the k-tool from the play store still no success.
There was a tool i found, NV writer tool, but that required for me to set the phone in Qualcomm mode, which was not an option for an I9100G with Texas Instruments OMAP processor. Still i tried the procedure, but the staps where i should have set the phone skipping the set to Qualcomm mode step (the *#something#* code was not working), and the app could not connect to the phone, so this was a stillborn solution for me.
I downloaded (kernel + rom), another stock rom (4.0.4), with Odin and repeated the process described above.
No imei and no baseband still.
I flashed the whole thing also i flashed the kernel again and the rom (this time i went back a step, to 4.0.3), also i used a PIT file for the SII i9100G model, and i did lfash from the a3 recovery mode the zip with the radio. Then i used a software, with the kind help of a friend, called Simlock Remote Server, where i have used a baseband + IMEI repair tool which was targeting my EFS partition and also it was flashing a stock i9100g EFS image. I have initiated quite a few of the of the operation mentioned before with the reair using the EFS image and also then i used another builtin functionality which could write the IMEI and baseband, still with a total lack of success.
I was sort of thinking that instead of an awesome phone i have a wery capable ipad, as all but the GSM functions were working. Sadly i have to say that i find myself in yet another problem. After flashing around 300 or so MBs are used on the system partition, where the rom resides. but after a while i notice heavy battery usage, even when not using my Galaxy S2 "iPad", and also the system partition is getting ever more full, till the whole 2GB are consumed and everything ceases to function. A factory restore with *2767*3855# solves the problem, but this will stard happening again after some time. I was thinking it could be a virus or something, as i have my phone rooted and installed a massive amount of applications which claimed miraculous IMEI repair abilities but failed miserably to deliver. I have installed 4 different anti-virus sw and these did not detect anything.
I am getting a bit scared of making this little piece of HW an useless transistor box, any advice and help would be appreciated. I am really ready to try anything, whatever platform Window$ or Linux may be necessary, please don't keep any possible solutions/suggestions from me.
Many thanks!

Flashed an incompatible ROM. Able to get into download mode. Now what?

I rooted my sprint Note 3 when I first got it three years ago and flashed it with a custom ROM. I used it for a year and then got a cell phone from work, so I basically stopped using the Note 3 except occasionally. I decided the other day that I wanted to try updating to a newer version of android on the Note 3. It's been a long time since I messed around with rooting, ROMs, and such, and I did not pay close attention to what I was doing and flashed a ROM that was incompatible. When I restarted, I got a Set Warranty Bit Kernel error. I can get the phone into download mode, but I'm unsure of what to do next to get it back to a usable state.
Is there a guide somewhere to walk me through this process?
Thanks!
Solved
Well, I got the phone working again. I basically followed this guide I found. I tried to paste in the link but I'm still too much of a noob. Anyway, it was on android central, and part of the url was how-flash-stock-rom-via-odin-new-interface. Hope that helps someone.
There was one step not covered in that guide - odin kept saying that the md5 value was invalid. I found a youtube video that said to change the extension of the firmware (it was .tar.md5, changed to .tar). After that, it worked and my phone is back.
Is there a guide somewhere to walk me through this process?
Click to expand...
Click to collapse
There's guides everywhere on this site! Just gotta find the right ones lol. Makes it that much better when you finally find em. Next time make a complete backup of your phone first. I like to use TWRP, you can download it directly from the Play Store. I got my Stock Firmware from this archive:
http://samsung-updates.com/device/?id=SM-N900P
Make a backup of that then flash away! It'll be a lot easier/faster to recover with TWRP. What ROM did you flash to yours? Just curious cause every one I've tried had multiple issues to where I wasn't even able to use half my phone smh. Then I root it with CF-Auto:
https://forum.xda-developers.com/showthread.php?t=2466423
Through Odin:
http://odindownload.com/download/#.WYX1A4jyuyJ
Then I make a another separate TWRP backup of my Rooted Stock Phone just in case lol. Lemme know if you run into problems again I'll try to help find it and/or fix it. The more problems I deal with the more I learn! :fingers-crossed:
Might wanna get a USB storage or something too cause ALL these backups take up time and space. (My external SD Card slot hasn't worked for awhile!)... does yours?

help with twrp and backups...

Hi, guys
my phone is Huawei p10 Lite (WAS-LX2)
Note: if you have a bricked huawei p10 lite of any kind (incl WAS-LX2) (or a NZ model)
and you want to know how i finally fixed mine, jump down to the end where it says
GOOD NEWS
quick synopsis: unlocked bootloader, flashed twrp, now i get an error (255) when trying to create backup using twrp..
you can read the rest if you want but the above basically covers it please help
so i have unlocked my bootloader and flashed twrp, before i did this i did a factory reset through androids settings, the phone is also only two months old.. but i cannot create a backup using twrp, it always fails in the same place when backing up data, does this mean my stock rom that has never been altered in anyway ect is somehow corrupt? wtf? i havnt even rooted it yet, i was going to make a backup first (of a known good rom.. lol)
i am assuming the data files are part of the rom? not something you can ignore.. they were one of the few things selected by default.. i have tried rebooting phone a few times, formatting sd card etc (64gb) so there is plenty of space...
any help would be much appreciated
the tutorial i was following is here: https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
my phones full build (or do i mean firmware number?..) number: WAS-LX2C706B170
android version 7.0
emui 5.1
any more info, just ask..
also, ive heard that once you have installed twrp/ unlocked bootloader you cannot use system update or androids factory reset without bricking your phone? is that true? otherwise i want to try that, i just want to root my damn phone already... or... its been a long time since i last rooted a phone... you dont need root to make a twrp rom backup do you? nah, surely not..?
or could my twrp install be corrupt? the tutorial said to drag and drop the downloaded file into cmd, but that wasnt working so i entered the location manually, it still appeared to install fine that way though so surely thats not it. i dont know
ok, i just bricked my phone... i did a factory reset in twrp, thinking it was... a factory reset... i googled whether it was safe first and everything came up clean... but it is not it wiped the os or something and now i just get a boot loop... what the hell? how could i be so stupid?! and how could twrp not warn me.. it was just a factory reset? and i havnt even rooted it yet, at this point i would probably prefer it was rooted in the hope their would be more options available to me to un brick it.. ok now i really need someones help.. why am i drinking and trying to watch tv while doing this, i am so stupid, this is the best and most expensive phone ive ever owned, what have i done?! sorry sorry ill calm down...
so if my firmware number is: WAS-LX2C706B170 then can i use one of these (also for huawei p10 lite) and if so what would be the difference? why are the numbers slightly different? same phone model, different firmware/ slightly...
here they are:
WAS-LX2C706B120
WAS-LX2C185B121
and they each had a OTA and a full firmware version too.
here is the link: https://romfirmware.com/2017/08/04/huawei-p10-lite-was-lx2/
but before i try these things, is there any saving my current stock rom? i dont understand how a factory reset could prevent it from booting properly..? its not actually bootlooping, it either gets stuck on logo, or goes to black screen but you can still see the volume slider when pressing volume buttons, see the home and back buttons (which do nothing) and hear the lock sound when you press the power button... still always a black screen though.. i guess its possible i knocked the format data button in twrp but im 95% sure i didnt. if i remove twrp and install stock recovery would i be able to get the stock rom working that way? or is there any way to do an OTA update/ fix as i havnt rooted it yet so it should be capable (except i cant boot to rom..) if i hold down all buttons it seems to try to do something... it says emui then goes to 4% then says software install failed: the update package does not exsist. please download the package again... reboot system now..? whats that all about?
ok, so i have found a possible solution but would like confirmation from someone who knows these things first...
i found this tool: Huawei Firmware Finder (Team MT)
link: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
and using this i have found my exact firmware, apparently straight from the official huawei update servers. the firmware number matches exactly, but there is no mention of it being for a huawei p10 lite so not 100% sure its a good idea, but if the whole firmware number matches perfectly and its the only one of its kind it must be the right one surely? and the size is the same as other huawei p10 lite firmwares..
here is the direct link:http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1514/g104/v89953/f2/full/update.zip
please someone else chime in to give me some advice...
is there any risk with flashing roms, or can i always still access twrp recovery to flash a new rom if i brick the phone?
cheers all
ok UPDATE:
i tried the repair file system option in twrp on the data partition just for fun (wrong word, im not having fun..) because i thought this rom was a lost cause..
upon reboot a huawei warning pops up saying the data partition has some serious damage and offers to try a low level format, it finishes successfully then restarts.
no change, still broken, but it offers to do a full format of data due to serious damage.
after restart phone boots fine, and enters setup wizard for first boot etc... perfect.
problem is, i still cant backup the data partition in twrp, still get same error:
createTarFork() process ended with ERROR: 255
bacjup failed..??
did i somehow get a brand new phone with a bad flash of a stock rom straight from the manuafacturer? with a slightly corrupted data partition... is there anyway to fix this? or can i assume the rom i downloaded from huaweis servers for my exact firmware is correct and i can use that as a backup in case i need it?
or in case my data is corrupt should i try to install that rom now?
or should i try to reflash twrp first and see if i can get a successful backup?
or should i just forget all this crap now my phone works and go straight to rooting it?
i really need some professional advice here.. lol
clearly i aint no expert
ok, so i noticed the frp was still locked for some reason so using adb, i relocked and unlocked bootloader, now frp is unlocked too, reflashed twrp, wiped dalvik cach/ cache, tried backup again...
no change, still fails on data partition, same error 255...?!
im lost,
close to trying to flash that rom i found...
or at least just rooting already..
OK UPDATE: first the bad news, then the good news:
so i gave up on backing up my data partition, as it was clearly somehow corrupt?...
so i went ahead and rooted my phone, everything was more or less working untill i used apps2sd...
that required several reboots and partitioning my sd card etc, then it said something about needing systemless root and a reboot, i went ahead with that and then my phone started bootlooping again, this time there was no fixing it, i of course tried removing sd card too.. nothing..
so i tried restoring to the rom i found using huawei firmware finder tool, that didnt work, using twrp to install zip, i got error -9? (couldnt find that one on the net..)
tried unzipping and putting update.app in dload folder on root of sd card, then booting to erecovery pressing vol- vol+ and power button, that also failed. now i was stressed near tears, this was the third day of research and trying to fix this... so i searche dhigh and wide, and gave up on stock roms, i figured that a custom rom designed for my chipset (hi6250)
and said to work on a huawei p10 lite then it should at least semi work on my phone, i did more research and the rom creator said to only use his version of TWRP to flash their ROM, so i reflashed to theirs... BIG mistake, if the custom recovery is the only thing you can boot into and the only way to access boot loader, do NOT risk losing it.. i did.. i lost my recovery..
so there for i lost my bootloader, so therefore i lost my ability to use ADB, or connect to pc in any way. i wanted to step in front of a bus at this point... but then there was:
GOOD news:
so i resorted to trying the official recovery roms on XDA for p10 lites, only i had been avoiding them as none of the build/ firmware numbers matched mine at all.. but i went ahead and clicked on the first download, (here is the link to post: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097) - you might find a few comments from me near the end there, lol..
anyway , once downloaded i unzipped and just pasted the dload folder straight to sd card and rebooted phone with all three buttons depressed. to my amazement when the huaei erecovery came up it started installing!!!? wow, i tried not to get my hopes up though..
first boot restarted after blue huawei splash logo, second boot went back to erecovery, offered factory reset and wipe cache(so i did), now it boots up perfectly every time like new, everything works! even gave me NZ language options etc, even though my build number didnt match any of those above, its still worked and even better it still shows all the correct information under about phone.
my build number was: WAS-LX2C706B170
so i can confirm it works for nz huawei p10 lites with 4gb ram and dual sim and WAS-LX2 builds
hope this helps someone else out there like me
tags: all official huawei rom,stock rom,twrp.stock,backup,official,rom finder,nandroid,back up, save,solution,fix,help,stuck,advice,simple,easy,guide,tutorial,root,huawei,p10,p10 lite,huawei p10 lite,was-lx1,was-lx2,firmware,iso,image,zip,file,download,error 255,255,error,createTarFork(),
Hey, just wanted to say thank you for posting this!
I'm from New Zealand, and have the exact same phone and the exact same issue.
Your "good news" section was exactly what I was looking for, and helped me fix my phone.
Cheers, George
update copy
Hi was wondering if you have a copy of the update you used as it is near impossible to get from the link on the other thread. Another Kiwi with a bricked phone.
All good, after 4 hours it finally downloaded. I will keep a copy in case anyone needs it. WAS-LX2

Categories

Resources