Related
Okay, I just rooted my brother's HTC Hero (GSM Unlock) and updated it to 2.1 Villain, but there were some bugs, like in the messages app, the key board wouldn't show up in a conversation. FB Sync wouldn't sync pictures to his contacts. Is there any way I can downgrade back to the original 1.5? If so, can anyone give me a link to download that .zip? thanks!
*note* I tried flashing the official 2.1 update, it failed
And what is a Nandroid backup? Can I restore it with that?
simonlcheng said:
Okay, I just rooted my brother's HTC Hero (GSM Unlock) and updated it to 2.1 Villain, but there were some bugs, like in the messages app, the key board wouldn't show up in a conversation. FB Sync wouldn't sync pictures to his contacts. Is there any way I can downgrade back to the original 1.5? If so, can anyone give me a link to download that .zip? thanks!
*note* I tried flashing the official 2.1 update, it failed
And what is a Nandroid backup? Can I restore it with that?
Click to expand...
Click to collapse
You really should have read up before just rooting and flashing. A nandroid backup is a backup of the phone so you can restore to how it was before you started to play with it.
You can download the rom you require here.
You should have done a Nandroid backup before trying to flash a new ROM, this is a MUST DO everytime you plan on messing around with the phone, it would simply let you restore the backup back to normal.
You need to do a full wipe of the phone and flash the new ROM posted above.
Jamie.
Can I just flash a stock rom of the HTC Hero generic? I flashed a rooted one, but I keep getting this notification about an OTA,I tried installing it, but it fails. If I flash a stock rom (if possible) can I install the OTA's?
I seem to be having somewhat the same problem.
Although I didnt flash my hero to that custom rom you're mentioning.
The problem is that I've been running the modaco 3.0 rom for quite a while and wanted to get the stock 2.1 rom.
I've tried to flash it using the HTC tool but couldn't be done. I accidently overrided my nandroid backup of the stock 1.5 rom so I found a stock 1.5 on modaco's forum and flashed it.
Now I'm running 1.5, build 2.73.405.5
Every time I wipe the phone and start from scratch (setting up the phone as if it was new) I get a notification about a new OTA update. When I try to update it, the phone resets (seems fine) and it ends up in Nandroid and doesn't get any further.
Then I chose to reboot the phone and the phone runs as normal but still no new firmware.
What am I doing wrong?
I've also tried the HTC tool for flashing the ROM but end up with a connection error (170).
I have of course wiped the phone but it doesn't help...
Pinnodyr said:
I seem to be having somewhat the same problem.
Although I didnt flash my hero to that custom rom you're mentioning.
The problem is that I've been running the modaco 3.0 rom for quite a while and wanted to get the stock 2.1 rom.
I've tried to flash it using the HTC tool but couldn't be done. I accidently overrided my nandroid backup of the stock 1.5 rom so I found a stock 1.5 on modaco's forum and flashed it.
Now I'm running 1.5, build 2.73.405.5
Every time I wipe the phone and start from scratch (setting up the phone as if it was new) I get a notification about a new OTA update. When I try to update it, the phone resets (seems fine) and it ends up in Nandroid and doesn't get any further.
Then I chose to reboot the phone and the phone runs as normal but still no new firmware.
What am I doing wrong?
I've also tried the HTC tool for flashing the ROM but end up with a connection error (170).
I have of course wiped the phone but it doesn't help...
Click to expand...
Click to collapse
I have the same problem! And when I do flash 2.1, the keyboard never appears when I go to the messages app. I just flashed an official stock 2.73.405.66 build, what if I do the OTA? Will it fail too? 'Cause I think it fails because last time, my phone was rooted.
Anyone got help? :-/
I have my phone set up just how i want it. How can i make it into a rom which i can flash when needed so i don`t have to keep reinstalling everything if i want to try out other roms then revert back to original state.
Thanks.
You just do a nand backup in cwm.
eg.I have roobox and gb nand backups.I just go into cwm and flick back and forth if I want.
Its a bit like system restore in windows.
Maybe I should change my question a bit. What I want is to make a rom of my unrooted firmware and apps
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I downloaded 5.0. Was NOT satisfied and put KitKat back on. No problems doing that at all but I an NOT rooted.
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
elesbb said:
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
Click to expand...
Click to collapse
Yeah I avoided lollipop all together. People seem to be having too many problems with it.I installed NK2 via Odin and now rooted/exposed. Runs smooth and I can flash other Roms.
But I do have this one issue. My auto rotation rodent seem to be working I tried everything I can think of. At first boot it works for 10 minutes or 5 sometimes. Than it shuts down completely. Accelerometer isn't working either. No temple run movement or asphalt 8 (sucks). I did sensor firmwate update and ran samsung diagnostic. The sensor seem to be at 0,0 on x and y axis. At first boot they work fine though. Any help please. I even tried different kernel and software Roms to no Vail. And I don't think it's hardware cause it works for brief moments.
Sent from my SM-G900T using XDA Free mobile app
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
tri0xinn said:
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
Click to expand...
Click to collapse
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Did the trick, thanks!
muniz_ri said:
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Click to expand...
Click to collapse
Does downgrading like this trips Knox?
Thanks
chiquito3 said:
Does downgrading like this trips Knox?
Thanks
Click to expand...
Click to collapse
I downgraded my wife's phone using the official 4.4.2 firmware from sammobile, and it did NOT trip knox.
I wanna try this, currently I'm on the B331 version with TWRP... So, should I just flash the stock recovery img? Then do the dload folder in the internal SD card put the UPDATE.APP there, press power up volume up + down so the phone can update itself... Then if (That's a big IF) the phone reboots fine, can I just reflash the TWRP again using adb? Am I right? Or there's something I'm missing?
carlosfl8 said:
I wanna try this, currently I'm on the B331 version with TWRP... So, should I just flash the stock recovery img? Then do the dload folder in the internal SD card put the UPDATE.APP there, press power up volume up + down so the phone can update itself... Then if (That's a big IF) the phone reboots fine, can I just reflash the TWRP again using adb? Am I right? Or there's something I'm missing?
Click to expand...
Click to collapse
Yours is the exact plan I have in the next month or so.
I went at this haphazardly because I all but gave up on this Honor 5X due to lousy scrolling and even lousier battery life because of that change 4 to 0 manual tweak to get the CORES right. Huawei messed that up badly.
What I did was rather rough but I flashed (via adb) an extracted STOCK RECOVERY.IMG to dump TWRP out-of-the-way and run a factory reset but encountered that nasty RED Exclamation Point a time or two.
Anyway I simply did the Dload FULL STOCK RECOVER via UPDATE.APP to get back to original STOCK and then grabbed the Marshmallow 6.01 UPDATE.APP (Latest with security updates) to climb back up to normal operation again.
Contrary to others I experienced NO BOOTLOOPS at all but everything proceeded well from the UPDATE.APP by pressing ALL 3 BUTTONS until EMUI began it's circle routine and rebooted perfectly to D351.
I did loose ROOT but will add that anytime as well as TWRP again later. For the time being just enjoying a whole better experience from smoother scrolling without the previous bumps and best of all, BATTERY LIFE no longer drains away like it used too.
Remarkable, hope some of that helps you get yours where you want it. MINE IS Kiwi-L24 by the way so theres no confusion on that.
So, I flashed the stock recovery, I created the ''dload'' folder and I put the UPDATE.APP in it, but when I try to flash it using the powe, volumen up + down, the phone starts well but it gets stuck at 5% till it reboots itself or ask me to reboot before telling me that ''system update failed'', any hints guys? I've been wondering if I have to put the folders (Cust / META-INF / patch / system) that come with the UPDATE.APP in the zip file as well in dload folder... Any help in this matter will be appreciate it...
Edit: Naaah, I'm done I spend the whole day trying to flash the new version even the stock firmware won't go pass 5%...
Mirror-Mirror said:
Yours is the exact plan I have in the next month or so.
I went at this haphazardly because I all but gave up on this Honor 5X due to lousy scrolling and even lousier battery life because of that change 4 to 0 manual tweak to get the CORES right. Huawei messed that up badly.
What I did was rather rough but I flashed (via adb) an extracted STOCK RECOVERY.IMG to dump TWRP out-of-the-way and run a factory reset but encountered that nasty RED Exclamation Point a time or two.
Anyway I simply did the Dload FULL STOCK RECOVER via UPDATE.APP to get back to original STOCK and then grabbed the Marshmallow 6.01 UPDATE.APP (Latest with security updates) to climb back up to normal operation again.
Contrary to others I experienced NO BOOTLOOPS at all but everything proceeded well from the UPDATE.APP by pressing ALL 3 BUTTONS until EMUI began it's circle routine and rebooted perfectly to D351.
I did loose ROOT but will add that anytime as well as TWRP again later. For the time being just enjoying a whole better experience from smoother scrolling without the previous bumps and best of all, BATTERY LIFE no longer drains away like it used too.
Remarkable, hope some of that helps you get yours where you want it. MINE IS Kiwi-L24 by the way so theres no confusion on that.
Click to expand...
Click to collapse
I'm gonna try this method, downloading the stock rom as we speak...
carlosfl8 said:
I'm gonna try this method, downloading the stock rom as we speak...
Click to expand...
Click to collapse
Hope it goes as smooth for you.
Either way post back and we'll try to step by step guide things the way they need to be to start your journey back to cycling back to normal again.
Hah ha, i was going to give my Honor 5X away but now i'm stuck on it again because the battery life is magnificient finally, something that was a real turn off before and of course the Lag is gone.
Looks like i will be re-Rooting it again and adding TWRP too very soon now. Once thats done the handset goes nowhere but my own usage. :good:
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