Related
Good evening/morning all
Just grabbed this new OTA from my One S so i thought i would make an appearance... And before anyone asks, yes - I am working on a ROM
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2
Please note: This OTA takes you from 1.53.401.2 to 1.78.401.2
Change log from the updater service (rather vague):
System enhancment
Enjoy
P.S > Had no time to analyse the actual content but the OTA contains full firmware updates including HBoot & Radio.
Edit: Just noticed paul has done a repack of the base already.. may still come in handy for you devs out there
I knew you would come just like I asked for and others.
Thanks Lee.
If you can work on a T-Mobile ROM/EU ROM.
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Can't wait for some goodness from you!
Sent from my US HTC One S using Tapatalk 2
Dimson75 said:
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Click to expand...
Click to collapse
Certainly will be
Sent from my LeeDrOiD One Xtreme loaded HTC One X
woohoo !! about time you made an appearance !! I knew you was hanging around here somewhere
missed you since i left the sensation forums
I know this is probably a really stupid question but I'm going to ask anyway...
Can you actually install an OTA package on the phone somehow or is it just useful to take files out of it?
And the other question, my phone doesn't find any OTA updates anymore since I've 'tampered' with it so is there a way to make it find and install the OTA updates again?
Thanks
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
LeeDroid said:
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
Click to expand...
Click to collapse
The other thing is that when I try installing the stock RUU it's telling me it's for the wrong device or something like that, although it's definitelly the correct RUU.
Also, my phone is HTCDev unlocked but is still S-ON so if I install the OTA package usign CWM is it going to update the radio and the hboot (I thought it can't do that if you're S-ON)?
Thanks
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Did'nt work for me, wrong CID...
edit the info.txt to match your CID
azzledazzle said:
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Click to expand...
Click to collapse
Ok, maybe I'm not getting this right but I'm talking about two separate things:
Issue 1. My understanding is that I can install the OTA zip package using ClockworkMod, is that correct?
Issue 2. The RUU package won't install on my phone:
i) I have restored via ClockworkMod the nandroid image of the stock ROM (image that I've taken straight after I unlocked the boot loader and flashed a custom recovery, but before I rooted the phone). Then, I flashed the stock recovery image using fastboot. So now my phone should be back to stock.
ii) I then tried to install RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
When I do this, the RUU goes through right up to the step where it says 'Updating signatures' and then it stops saying 'unknown error' and it leaves my phone on that screen with black background and white HTC logo. Then, I have to hard boot and the phone starts up fine but in the state it was before the RUU - not even the user data is missing. To me this means that for some reason it doesn't even try to flash the RUU onto the phone but it stops when checking the signatures - I just can't understand why this is happening...
Can you help?
Thanks
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
azzledazzle said:
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
Click to expand...
Click to collapse
Sorry for my ignorance, but how do I initiate the installation of the OTA zip package using the stock recovery? As I said, I can't actually get it 'over the air' but I've just downloaded the zip package from this thread...
ok put the package on your sd card.
boot into fastboot, flash the stock recovery using the command ''fastboot flash recovery recovery.img'' (or recovery_signed.img) (also no quotes)
when thats done, select recovery from fastboot using volume button..
When you get a red ! press volume UP and power button, That will take you into stock recovery
Then look for the option, install from sd card or something like that
select your OTA package and BOOM !!! job done
Reflash CWM and away you go
Damn... I had no idea that you can actually get into the menu of the stock recovery... It all makes sense now...
me neither till about 3 days ago
I might not seem like a noob,,,,,but deep down i am
azzledazzle said:
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
Click to expand...
Click to collapse
I've tried that again and it actually breaks down when it gets to 'Checking Header...' and it exits with 'ERROR [155]: UNKNOWN ERROR". Maybe this is a bit more specific...
this is what i found for error 155
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator".
Or use the rom.zip -> PGXXIMG.zip flashing method.
Click to expand...
Click to collapse
I dont know if it will fail when flashing the rom.zip in CWM - usually you have to rename it to the model number and flash in fastboot, however you cant do this with S-ON
I bought a used TF300T, 16GB
Unlocked
It has TWRP 2.4.4.0, JB 4.2 bootloader, and EnergyROM 3/28 10.6.1.8
Kernel 3.1.10-g59bc3cb
I was wondering if I should leave it alone, or restore it to factory. Is that even possible?
If I keep it as it is, how do I update?
I knew I should have bought a virgin Asus, lol.
Thanks for any info!
You can restore it to factory by flashing a stock Asus blob in recovery (I recommend using the 10.6.1.8 ROM since that was the last one on your tablet). It will wipe all data, including whatever's on the internal storage. Once you get that set up, flash the OTA updates incrementally to avoid issues (there are only two updates to flash). You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be.
All the blobs you need should be on Asus' website. If you need more help, there are lots of "how to flash back to stock" threads with instructions. Just read carefully, and if you decide to flash a custom recovery when you're done, DO NOT flash one with "-JB" at the end of it or you could brick your tablet. You will need a recovery that ends in "-42". Be absolutely sure, because there are 3 different bootloaders for the TF300, and flashing one from either of the other bootloaders will brick your tablet.
EndlessDissent said:
...You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be...
Click to expand...
Click to collapse
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
skank_boy said:
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
Click to expand...
Click to collapse
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
EndlessDissent said:
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
Click to expand...
Click to collapse
Okay, I will try again. Maybe three times the charm. Thanks!
skank_boy said:
Okay, I will try again. Maybe three times the charm. Thanks!
Click to expand...
Click to collapse
You've flashed the stock blob in TWRP twice already? You're not flashing TWRP afterwards, are you? I've flashed a stock blob in TWRP, and I had the stock recovery afterwards. Are you rebooting into Android after you flash it?
I tried to flash, it failed....BUT this time it worked (??!!) lol.
Obviously I wasn't doing something right, but I have now. I installed 10.6.1.8, now on to the next in the normal manner.
Thanks again!
Tried to boot in to recovery to flash a root zip..
When i volume up to enter recovery, screen goes black. I hit power button and TWRP opens but its unusable and dual screen..top and bottom. Slide to unlock is on the screen but nothing works. Only way out is to hold down power and reset.
Help!
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
DatacomGuy said:
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
Click to expand...
Click to collapse
What bootloader are you on (its in settings app)
cmendonc2 said:
what bootloader are you on (its in settings app)
Click to expand...
Click to collapse
10.6.1.8-20130225
DatacomGuy said:
10.6.1.8-20130225
Click to expand...
Click to collapse
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
cmendonc2 said:
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
Click to expand...
Click to collapse
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
DatacomGuy said:
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
Click to expand...
Click to collapse
I know you can use that firmware to install KitKat ROMs as shown here (http://forum.xda-developers.com/showthread.php?p=49028315).
Use the 10.6.1.27.5 firmware with this:
Tylorw1 said:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Click to expand...
Click to collapse
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
DatacomGuy said:
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
Click to expand...
Click to collapse
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
cmendonc2 said:
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Alright..
fastboot -i 0x0B05 flash recovery firmwarefile.zip
Click to expand...
Click to collapse
Is that the right syntax?
DatacomGuy said:
Alright..
Is that the right syntax?
Click to expand...
Click to collapse
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
cmendonc2 said:
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
Click to expand...
Click to collapse
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
fastboot -i 0x0b05 flash US_epad-user-10.6.1.27.5.zip"
Click to expand...
Click to collapse
and i get:
Unknown partition 'US_epad-user-10.6.1.27.5.zip'
error: cannot determine image filename for 'US_epad-user-10.6.1.27.5.zip'
Click to expand...
Click to collapse
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
DatacomGuy said:
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
and i get:
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
Click to expand...
Click to collapse
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
EDIT2: Is this the right one?
openrecovery-twrp-2.6.3.0-tf300t-JB.blob
DatacomGuy said:
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
Click to expand...
Click to collapse
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
cmendonc2 said:
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
Click to expand...
Click to collapse
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
DatacomGuy said:
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
Click to expand...
Click to collapse
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
cmendonc2 said:
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
Click to expand...
Click to collapse
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
DatacomGuy said:
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
Click to expand...
Click to collapse
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
cmendonc2 said:
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
Click to expand...
Click to collapse
i dont want to flash any rom right now, i just want to stick with stock 4.2.1...
Last time i flashed TWRP.. albeit incorrectly.. it didnt ask anything when i rebooted into recovery. I'm assuming thats when it asks....
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
vaindil said:
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
Click to expand...
Click to collapse
you CAN NOT install an ota when you are not fully stock. you will receive an ota, but it will always error out. you have to be completely stock to update via ota. by completely stock i mean completely, not even a build.prop edit. busybox is not stock.
simms22 said:
you CAN NOT install an ota when you are not fully stock. you will receive an ota, but it will always error out. you have to be completely stock to update via ota. by completely stock i mean completely, not even a build.prop edit. busybox is not stock.
Click to expand...
Click to collapse
I just uninstalled busybox and tried again, but I'm unfortunately getting the same error. I know that custom recovery and root are safe for flashing an OTA update, and they're the only two remaining non-stock things I have on the device.
Flashed stock boot.img again and this time also included stock system.img, then the OTA update flashed properly.
vaindil said:
Flashed stock boot.img again and this time also included stock system.img, then the OTA update flashed properly.
Click to expand...
Click to collapse
Haha ha. Crazy. If you were going to Flash a stock system.img, why not flash the 4.4.3 one?
Sent from my Nexus 5 using Tapatalk
Rename the files after uninstalling Franco kernel
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
vaindil said:
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
Click to expand...
Click to collapse
harrysummer said:
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
Click to expand...
Click to collapse
Thanks a lot for this suggestion.
I removed xposed, SU and franco kernel but was stuck at this issue.
Renaming the files did it.
Thanks once again.
No need to remove SU
You are doing almost the same thing as I did. I was using supersu. And, I found that SU do not bother the update, because it do not modify any files in the system. However, the update will remove the su binary automatically...
nirmit14 said:
Thanks a lot for this suggestion.
I removed xposed, SU and franco kernel but was stuck at this issue.
Renaming the files did it.
Thanks once again.
Click to expand...
Click to collapse
harrysummer said:
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
Click to expand...
Click to collapse
Thanks! That solved it for me
Sorry for the thread revival, but I'm in the same boat. I am using Linaro kernel however, which is a Franco spinoff if I remember correctly. Would the above mentioned page with fix of filenames for Franco, fix my issue as well?
Mysticodex said:
Sorry for the thread revival, but I'm in the same boat. I am using Linaro kernel however, which is a Franco spinoff if I remember correctly. Would the above mentioned page with fix of filenames for Franco, fix my issue as well?
Click to expand...
Click to collapse
Things have changed. You must be fully stock now, including recovery. As before, stock kernel etc. You're best just flashing the updated system.img and boot.img, or one of the rom.zip
I have a thread about this in my signature.
rootSU said:
Things have changed. You must be fully stock now, including recovery. As before, stock kernel etc. You're best just flashing the updated system.img and boot.img, or one of the rom.zip
I have a thread about this in my signature.
Click to expand...
Click to collapse
I've flashed in stock system.img, and stock boot.img. Just finished re-doing it via NExus Toolkit. The latest error I am getting is the thermal engine system error. This led me to think I need to rename the files, as per the instructions about Franco, as people were saying even AFTER putting on stock system.img, these files remained?
Mysticodex said:
I've flashed in stock system.img, and stock boot.img. Just finished re-doing it via NExus Toolkit. The latest error I am getting is the thermal engine system error. This led me to think I need to rename the files, as per the instructions about Franco, as people were saying even AFTER putting on stock system.img, these files remained?
Click to expand...
Click to collapse
1) please done use toolkits. Its simple enough to do manually
2) these files exist in stock anyway
3) if you're flashing stock system image, why not just flash the latest then it won't matter?
rootSU said:
1) please done use toolkits. Its simple enough to do manually
2) these files exist in stock anyway
3) if you're flashing stock system image, why not just flash the latest then it won't matter?
Click to expand...
Click to collapse
I flashed system.img, and boot.img. I did not install 5.0 completely. I am just trying to repair my main system/recovery/boot files to work with the normal OTA.
Mysticodex said:
I flashed system.img, and boot.img. I did not install 5.0 completely. I am just trying to repair my main system/recovery/boot files to work with the normal OTA.
Click to expand...
Click to collapse
Sorry, no idea what you're talking about now or what the problem is.
rootSU said:
Sorry, no idea what you're talking about now or what the problem is.
Click to expand...
Click to collapse
nirmit14 says he had to rename two files, most importantly thermal-engine-hh.bak, however Is am not quite sure how to get access to these files, so I ask for advice on that.
Thanks.
Mysticodex said:
nirmit14 says he had to rename two files, most importantly thermal-engine-hh.bak, however Is am not quite sure how to get access to these files, so I ask for advice on that.
Thanks.
Click to expand...
Click to collapse
If you flash the kernel, it renames existing STOCK thermal-engine-hh to thermal-engine-hh.bak then creates new thermal-engine-hh. OTA Will not work with new thermal-engine-hh so you must delete that and rename STOCK thermal-engine-hh.bak Back to thermal-engine-hh
HOWEVER, if you flashed system.img like you said, then you only have STOCK thermal-engine-hh (because it is in system.img) and have NO thermal-engine-hh.bak at all.
So the answer to your question is irrelevant as you don't need to.
As for now you rename system files, options are
- root explorer
- adb shell
- file manager in recovery
But just flash 5.0 system.img and boot.img and be done with it.
I had originally manually flashed system.img and boot.img, and the file is there there.
I have sinced pulled the file onto my PC, renamed it, and pushed it back on. I will try the OTA again.
Mysticodex said:
I had originally manually flashed system.img and boot.img, and the file is there there.
I have sinced pulled the file onto my PC, renamed it, and pushed it back on. I will try the OTA again.
Click to expand...
Click to collapse
The. Bak file was still there? Assume you didn't wipe system when you flashed it then
rootSU said:
The. Bak file was still there? Assume you didn't wipe system when you flashed it then
Click to expand...
Click to collapse
Correct, everything was left on, I simply flashed the img files from the factory image. I assumed it would just overwrite it system.img.
Flashing recovery.img removed TWRM, so I thought the others would do the same.
Edit: Reflashed system.img using Nexus toolkit, and now the OTA took. I had confirmed that this flashing did remove the thermal file entirely. Still not sure what modified it, but I'm guessing it's Linaro kernel.
Im trying to make recovery on my lg d800 by this guide http://forum.xda-developers.com/showthread.php?t=2633150
and im getting this error [URL=http://www.siz.co.il/]
[/URL]]
Anyone know how to fix?
maozer said:
Im trying to make recovery on my lg d800 by this guide http://forum.xda-developers.com/showthread.php?t=2633150
and im getting this error
Anyone know how to fix?
Click to expand...
Click to collapse
Copy and paste one line at a time... looks like you copy/pasted a block of commands within the adb shell and things didn't paste properly.
-Daryel
daryelv said:
Copy and paste one line at a time... looks like you copy/pasted a block of commands within the adb shell and things didn't paste properly.
-Daryel
Click to expand...
Click to collapse
Ok i did it and now im getting error [-] Loki aboot version does not match device.
I tried this files:
openrecovery-twrp-2.6.3.2.img
openrecovery-twrp-2.6.3.3-g2att.zip (extracted and copy img file) here im getting error "input file is not a loki image"
openrecovery-twrp-2.6.3.1-g2att.img
openrecovery-twrp-2.7.0.0-d800-loki.zip (extracted and copy img file) here im getting error "input file is not a loki image"
All from this post: http://forum.xda-developers.com/showthread.php?t=2449670
I dont know if it matters but i should mention what i did.
1.Bought d800 ATT 4.2.2
2.Rooted it
3. Installed twrp recovery
4.Installed kitkat rom
5.Rooted it and installed twrp version 2.7 with autorec
6.Installed costume rom (sopk)
7.Installed costume rom cloudy 3g.
8.Restored back to stock 4.2.2.
Coundt install costume recovery since then. everytime i go to recovery there is a blank screen and needed to reset.
Big thanks for help!
maozer said:
Ok i did it and now im getting error [-] Loki aboot version does not match device.
I tried this files:
openrecovery-twrp-2.6.3.2.img
openrecovery-twrp-2.6.3.3-g2att.zip (extracted and copy img file) here im getting error "input file is not a loki image"
openrecovery-twrp-2.6.3.1-g2att.img
openrecovery-twrp-2.7.0.0-d800-loki.zip (extracted and copy img file) here im getting error "input file is not a loki image"
All from this post: http://forum.xda-developers.com/showthread.php?t=2449670
I dont know if it matters but i should mention what i did.
1.Bought d800 ATT 4.2.2
2.Rooted it
3. Installed twrp recovery
4.Installed kitkat rom
5.Rooted it and installed twrp version 2.7 with autorec
6.Installed costume rom (sopk)
7.Installed costume rom cloudy 3g.
8.Restored back to stock 4.2.2.
Coundt install costume recovery since then. everytime i go to recovery there is a blank screen and needed to reset.
Big thanks for help!
Click to expand...
Click to collapse
How did you restore back to 4.2.2? What method? Did you just flash a D800-10d ROM? Or did you use LGFlashtool to go back to 4.2.2? My feeling is that you have something mismatched. Best advice to go back to 4.2.2 if you were on 4.4.x is to use the TOT method and LGFlashtool. That will restore lall the phone's partitions back to proper versions.
-Daryel
daryelv said:
How did you restore back to 4.2.2? What method? Did you just flash a D800-10d ROM? Or did you use LGFlashtool to go back to 4.2.2? My feeling is that you have something mismatched. Best advice to go back to 4.2.2 if you were on 4.4.x is to use the TOT method and LGFlashtool. That will restore lall the phone's partitions back to proper versions.
-Daryel
Click to expand...
Click to collapse
I restored from 4.4 to 4.2.
I just used the backup i made when i got the phone. in recovery went to restore..
Its possible to use lgflashtool now? and do some kind of hard reset? it will be ok then?