Hello Guys,
Earlier today I decided it'd be a good idea to act like an idiot and flash a ICS rom over top my gingerbread install on my RAZR. It booted, but it'd crash every minute or so. Since then, I've been struggling with it. I couldnt get any other roms to flash, so I ended up trying to use fastboot to go back to stock. First up, using RSDLite5.6 and "VRZ_XT912_6.5.1-167_DHD-14_M2-5_CFC_1FF_01.xml.zip", I had an error about "OEM" somethign something- I got around that by removing the 2 lines referencing the OEM in the xml. With the same file, trying again, I got to where it would flash webtop and received errors. Lost, I kept looking- but at this point, my battery is almost dead. I found an article about flashing with a low battery using EternityProject's FastBoot. I've got that to go through successfully 100%- as you can see in the following screenshot. My phone now takes all of the data and writes it properly, reboots on the command, but just sits at the motorola logo.
Any advice? At this point i've actually tried 3-4 different "stock" fastboot files and both RSDLite5.6 and the eternityproject's fastboot flashme. Nothing.
hxxp://i.imgur.com/sr8AL.png <- replace xx's
Thanks guys.
Try going into stock recovery via the fastboot menu and do a data+cache wipe. If not make sure you are using the correct fastboot for your phone. Also I believe there are certain ICS leaks that cannot be downgraded from so you should look into which one you flashed and if/how there is a way to downgrade from it.
[FIXED]
Got some help on the forum;
downloaded asus firmware, unpacked blob, fastboot flash staging blob; fastboot reboot
Prime is now back to fully operational!
Many thanks to @kkdm
[/FIXED]
Hello,
I have looked around the various threads (including the 'how to unbrick your prime' one) but have not seen this issue mentioned.
I have a strange issue where if I factory reset (i.e. to Asus) the device will simply keep looping at the ASUS EEE logo, with device is unlocked in the top left hand corner. If however I install CM10 or another MOD, it seems to work as normal and boot into the homescren.
Having read around, there was an issue with an Asus update where it appeared to do something similar to this, is it perhaps that I am on that version and thus am getting the same error? Would a simple download and copy of the latest ASUS ROM fix that? I am unsure on how to do this exactly, but have read this was an issue, but I find it unlikely as everything was fine before I unlocked etc.
Is it perhaps the bootloader has become corrupt in some way with the ICS/JB difference? This is just a guess on my limit knowledge...
The reason for putting back the ASUS stock ROM is selling the device, having upgraded to the Infinity, and do not particularly want to send it with CM10 on.
Any help would be greatly appreciated,
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
It turns out there is no ROM on the internal storage anymore (I must have selected the format option on my last attempt at installing Androwookie), as a result I cannot access the sdcard by plugging the thing into my PC.
Is there a way of installing this via the micro SD card slot?
flumpster said:
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
Click to expand...
Click to collapse
Hello,
Just to clarify, I can get into recovery without issue, it just won't boot after factory reset and now hangs at ASUS logo.
Is there a way around this at all? :--(
Hello,
Latest problem is having ASUS Transformer Prime ADB Interface listed in Device Manager, but not being able to use the adb shell.
I get either 'device not found' or occasionally something about /system/sh not being found, in either case this is obviously not good.
I can still get into TWRP 2.1.3 though, surely there must be a way round this?
Now fixed, see first post
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Twinning92 said:
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Click to expand...
Click to collapse
CWM is not compatible with Jellybean. Unfortunately you are hard bricked.
Why didn't you make a backup with NvFlash? If you did that you could restore your tablet.
Hello,
I have an S-on 4g LTE unlocked with bootloader and running Viper 2.2. I've been getting those annoying update messages, so I thought I'd try a different ROM. I tried to switch to the Avatar ROM on the forums: http://forum.xda-developers.com/showthread.php?t=2207395, but I couldn't get it to take. I read somewhere that I needed to extract and load the boot.img file through ADB first, so I did that but it still didn't take. I could install the ROM, but I can't get it to boot past the "HTC: This build is for development purposes only" screen. It hangs there for a while, then the screen goes black, and eventually it loops back.
So then I decided to just go back to Viper 2.2, but that won't take. It's doing the same loop-back. I did a full backup before starting, so I tried restoring that but it made no difference. I thought maybe I needed to do the adb boot.img thing again using the boot.img file from the viper 2.2 file, but there's no boot.img in any of the viper files I have. So I tried looking on the forums, but all the boot.img file links I found were expired/dead/long gone.
So I need some help in figuring out how to get this phone back. I can get it out of the bootloop by pulling the battery and then do hboot via the downvolume + power button, and then I can get into teamwin recovery from there. But after that, I don't know what to do. Any advice/help to get back on my feet would be greatly appreciated!
Nevermind...got it! I tried installing the stock kernel from here http://forum.xda-developers.com/showthread.php?t=1770978 and it booted back up finally.
I kind of thought that's what I needed to do, but I was at the point where I didn't want to keep touching (or more like breaking!) more stuff until I knew what to do. Thanks anyway!
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