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
Related
Hello,
If anyone could help me get my phone back into a functioning state, I would very much appreciate it! I have been playing around with the Cyanogenmod 10 nightlys. All was going well until I decided to try encryption. It encrypted the phone okay, but I decided to format the phone and get it back to an unencrypted state, except it wouldn't allow me to factory reset. The button to start the reset did nothing except reboot the phone a few minutes after pressing it.
No problem, I thought, I made a nandroid backup before I started playing with ROMs, I'll just restore that, except that didn't work because CWM couldn't mount the encrypted volumes. So, I copied the CWM backups to an SD card using root explorer, and tried to restore from there. It gave me an error advising it couldn't mount/format /system. So, I rebooted, only to get stuck on the Samsung boot logo.
I can still get into download mode though. so I tried flashing the stock firmware with Odin. Odin reported the software flashed succesfully, and the phone boots now with the stock animation so presumably it did work, but it still asks for the encryption key. I put in the key I used originally but it rejects it.
I don't know what else to do to restore my phone to a stock state.
This is my first Android phone and I was just playing around out of curiosity, so pleas excuse any noob errors I may have made along the way. I shall be sure to learn from them.
Please tell me I can get my phone back to the original state!
s0mmie said:
*snip*
Click to expand...
Click to collapse
It seems I have managed to get back to a working state by using the Android recovery menu. Phew. I shall not be messing with encryption again. All part of the learning curve though, I suppose!
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
Hi Everyone,
I unlocked the bootloader a while back, planning to root and install 3rd party roms, but I never ended up doing that.
I only played around with removing "Unlocked Bootloader" message, and that's all. It took a trip to Motorola and came back once, is it possible they removed recovery?
Anyway, is there anyway to revive the device? It boots fine but I am having issues with google play store, it keeps crashing so I wanted to do factory reset, that's when I realized that recovery is missing.
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
PseudoDev said:
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
Click to expand...
Click to collapse
Hi, it went to motorola because the SIM slot pins were bent, of course it came right back with a little note "sorry, bootloader unlocked, we won't fix it" basically bootloader unlocking also voids all physical/mechanical warranty as well, I understand, I shouldn't have unlocked the bootloader on day 1 and get the sim slot messed up on day two, ended up with $50 paperweight.
Thank you so much for the suggestions, I don't want to mess it up more than it already is.
It's a CDMA+GSM edition, supposedly identical to Verizon model. I think I already have adbfastboot, I should be safe following this video here, unless you have any other suggestions
https://www.youtube.com/watch?v=R4c0fO8Kr_Q
Thanks again.
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
xpmule said:
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
Click to expand...
Click to collapse
Thanks, I managed to get TWRP to work on the device using ADB Fastboot, and I got the phone rooted. I removed the old Google Play store manually, restarted, and then installed it from apkmirror, and now everything seems to work just fine, but somehow I think stock recovery image is gone, I don't think I have the factory image anymore.
I checked around but couldn't find it, would you happen to know what is the stock rom for XT1526?
Thanks.
Like i was saying just look it up as per your model number..
And glad you got it working.. that is all that really matters.
Plus that screen that shows the Droid Operation with the words "no command"
that is the stock recovery.. if you installed TWRP you should never see that booting recovery.
See what i mean ?
So check this page.. it's where a lot of us got our Firmware from.
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
But research your phone model first and see what people are saying.
Mine has a tab of little plastic cover paper that pulls out that shows my Model number.
Or get it from the bootloader screen then look around using search to see what people are saying.
Some of them have restrictions.. and some are GSM versions which are a bit different.
I am not too familiar with your phone version but i Google'd it and i see Sprint & Boost coming up..
Such as this topic..
http://forum.xda-developers.com/moto-e-2015/general/moto-e-2015-cdma-sprint-xt1526-custom-t3241117
Basically i don't want to say hey go flash firmware then see you have problems
And all i did was go to that Firmware page and search for the model number
by hitting ctrl+F with Firefox then cycle through them.
There is a few of them.. that follow a file name format.
XT1526_SURNIA_ACG_5.1
ACG would be the region part of it or provider such as Boost
So that page has 16 versions of Lollipop for your model number.
What i would do is ask guys on the firmware topic what one they used.
This is where i got the Filefactory link on post one (you can look in the Mega links too)
http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
I would search through that topic and ask on that topic what others used.
Then search around the forum (General section or maybe help section) and then with Google too.
For example, i googled this "XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.8_cid9_subsidy-DEFAULT_CFC.xml.zip"
And it showed this topic..
http://forum.xda-developers.com/mot...nt-version-t3052844/post64438539#post64438539
Research.. better safe than sorry LOL
Thanks for all the info, sometimes was messed up because phone received an update from Google and when it attempted to update, it got stuck in recovery (would not update). Was there a notice somewhere that we shouldn't update the phone? Anyway, it kept trying to reboot the phone after it turns on but it gets stuck at TWRP and won't update.
I was able to get into the settings and wipe the phone, now I am trying to go through set up again, but I think my best bet is to flash stock firmware and start over. Next time instead of trying wipe, I can just reflash stock firmware over it.
So after updating my bootloader to the new version so I can run Android Nougat however I wasn't getting any LTE connection and decided to restore the EFS backup I had from android MM.
My phone started having problem more problems (SIM card not being detected) and I decided to run the OPX recovery and switch back to default.
However this resulted in my bootloader getting locked for some reason and whenever I try to reboot my phone the screen is black and the LED indicator turns white.
I can boot into the factory OPX recovery but I'm forced to use the volume and lock buttons because I can't use my touchscreen whilst using this (no idea whether this is normal).
I can still boot into fastboot mode and have tried to sideload a new ROM however this has been to no avail.
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Hmm, okay thanks for your reply. But is it really a hardware problem? It sounds weird but maybe replacement is a way...
It strange, since I had the problem with my phone there are 3-4 new threads now in this forum were people have exactly this problem, black screen with white led.
I will not flash my phone again in the foreseeable future and just use gravitybox instead.
Mutchatcho said:
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
Click to expand...
Click to collapse
I did the exact same thing as you and ended up in this situation.
adefigo said:
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Click to expand...
Click to collapse
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Miniheadshot said:
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Click to expand...
Click to collapse
With the new mainboard and the new rom build, it is impossible to use twrp or root. I didn't know that when I wrote I would be using gravitybox from now on and not flash custom roms again.
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Mutchatcho said:
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Click to expand...
Click to collapse
What is your built number?
adefigo said:
What is your built number?
Click to expand...
Click to collapse
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Mutchatcho said:
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Click to expand...
Click to collapse
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Ah okay, I didn't know that. Obviously then I got maybe the other one.. but not sure if this makes the difference.
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
dchrono said:
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
Click to expand...
Click to collapse
No, did not change twrp versions during flashing new ROM and wipe to restore backup. Don't know if I remember correctly but I think I was on Bluesparks twrp (was it 3.0.0?) and did not change that during the processes.
i also had same problem
i try to update my twrp recovery with flashify. it was successful but now i cant boot into recovery. i dnt know bootloader is locked or not. i can use many fastboot commands like fastboot reboot-bootloader, fastboot continue. please help me. i try many times to update or remove twrp but nothing happend. rom is working.
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
I never changed twrp version during this until it was removed by MsmDownloadTool.
I also noticed that adb sideloading using OOS's old stock recovery with a OOS OTA zip doesnt work, it either gets stuck at logo or loops. Sideloading newer OTA zips kills the phone more because I tried to flash a MM zip and found that recovery no longer works. I've tried redownloading the MsmDownloadTool package and using this other modified MsmDownloadTool here a few replies down https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Another thing I noticed is that windows detects a bunch of unreadable local drives, with one readable containing only an 'images' folder, with useful-looking stuff like adsp.b00, adsp.b01 all the way to adsp.b12 and also .mbt files. I can provide the full list if it's useful. It's also detected in the device manager as "Marshall London HS-USB Diagnostics 9006 (COM6)" under Ports.
I really hope that I don't need to send this phone back to oneplus.
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
Click to expand...
Click to collapse
Exactly what I did and what happened to my phone. I had to send it back to repair and got it back with a new mainboard in a state that I cannot use twrp any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Did you try to adb sideload flash the 3.1.4 on the 14 version?
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt phone back to oneplus.
Click to expand...
Click to collapse
I had flashed a ROM and wanted to restore a backup of MOOS. The back up restored no problem but when I booted it wouldn't detect sim trays and no wifi. When I typed *#06# no iemi's and finally when I checked about phone I had no baseband. I had a back up of efs and persist but wouldnt help. If this sounds like your issue or if anyone's having this problem its actually easy fix. With adb commands had to delete modem1 and modem2 files. I had my doubts but after reboot sims trays detected, wifi and iemi's restored.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.