Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.
redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)
MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.
Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2
Related
I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.
You can get the update in the "Just got an OTA update" thread.
Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk
...................
martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...
for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.
TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk
Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...
Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.
None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116
Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.
Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.
Hi people. thinking of unlocking, but afraid of brick. my tablet is funny.
every update that came through, never auto installed. Had to do it manually.
ALSO, voodoo never worked.
stock Rom, locked, jelly bean.
thinking of unlocking to regain root.
i miss it!
Thanks
redheadplantguy said:
Hi people. thinking of unlocking, but afraid of brick. my tablet is funny.
every update that came through, never auto installed. Had to do it manually.
ALSO, voodoo never worked.
stock Rom, locked, jelly bean.
thinking of unlocking to regain root.
i miss it!
Thanks
Click to expand...
Click to collapse
You don't need to unlock to get root back. Since your OS is iffy, I suggest to should do a clean flash and put everything back to normal.
Yes. i heard only way to root was to unlock JB was downgrade, then reroot. but, i don't know if voodoo would work after update. it's failed 3 times
redheadplantguy said:
Yes. i heard only way to root was to unlock JB was downgrade, then reroot. but, i don't know if voodoo would work after update. it's failed 3 times
Click to expand...
Click to collapse
I will make it work for you. Downgrade back to .30, re root, now here is the trick part, after you root, you should have superuser on your device, open up superuser(keep it open), then download rootcheck from the market to verify that you have root, now download superSU from the market, open it up, it will do the update.Now download Voodoo OTA root keeper, open it up and verify that all the boxes does have check mark to it except one, when you click save button the last box will be checked and now you have the option to "temp" unroot, click on this to save root. Go back to your notification, then click update to JB. Your device will shutdown and do the upgrade. Once it's done, open up OTA root keeper and click restore, bam you have root back.
Cool. how do i downgrade without unlocking
redheadplantguy said:
Cool. how do i downgrade without unlocking
Click to expand...
Click to collapse
Very simple:
Download .30 from Asus website, unzip it, now you have a zip file called EP201_768_SDUPDATE
Copy this to the root of your external sdcard, put it back to your device.
Turn off your tab. Hold down volumedown+powerbutton to get to stock recovery and once you see the white text displayed,let go both buttons, it automatic downgrade for you.
If you copy the file to the root of your internal sdcard then you just reboot and it will install for you.
thank you. gonna try this right now. I'll let you know in a bit.
buhohitr said:
Very simple:
Download .30 from Asus website, unzip it, now you have a zip file called EP201_768_SDUPDATE
Copy this to the root of your external sdcard, put it back to your device.
Turn off your tab. Hold down volumedown+powerbutton to get to stock recovery and once you see the white text displayed,let go both buttons, it automatic downgrade for you.
If you copy the file to the root of your internal sdcard then you just reboot and it will install for you.
Click to expand...
Click to collapse
Didn't work. Unzipped file was named something else, I renamed it to what you said. White letters came up, I let go, and there was 4 tiles on screen. One said rck, one Android, one USB, one wipe data.
Tried again with original filename. Downgrading now.
(hopeful)
redheadplantguy said:
Didn't work. Unzipped file was named something else, I renamed it to what you said. White letters came up, I let go, and there was 4 tiles on screen. One said rck, one Android, one USB, one wipe data.
Tried again with original filename. Downgrading now.
(hopeful)
Click to expand...
Click to collapse
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
buhohitr said:
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
Click to expand...
Click to collapse
Us_epad-user-.9.4.5.30
It downgraded wiped all data too. Rooted and getting ready to try your advice about updating. I never heard i had to temp unroot first. Good luck to me. I'll let you know
buhohitr said:
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
Click to expand...
Click to collapse
Crap. Lost root when updated back to jelly bean. Tried twice. Voodoo has no checkmark by protected copy available. Might take it to best buy. I have 2 year plan on it.
Tried a 3 rd time cause I thought manually updating many have been a problem, but "check for update" still shows none. Anytime firmware came through, never auto updated. They always failed.
Thinking of just returning it and have them get me another
redheadplantguy said:
Crap. Lost root when updated back to jelly bean. Tried twice. Voodoo has no checkmark by protected copy available. Might take it to best buy. I have 2 year plan on it.
Tried a 3 rd time cause I thought manually updating many have been a problem, but "check for update" still shows none. Anytime firmware came through, never auto updated. They always failed.
Thinking of just returning it and have them get me another
Click to expand...
Click to collapse
You only can do manual downgrade to .30, but you must do OTA update from .30 to JB to preserve root. If you manually upgraded, it will wipe everything before upgrade. After you finished manual upgrad with .30 and when the os came up, and you connect it to the internet it should automatically download JB to your device and prompt you to upgrade, this is not happening??
buhohitr said:
You only can do manual downgrade to .30, but you must do OTA update from .30 to JB to preserve root. If you manually upgraded, it will wipe everything before upgrade. After you finished manual upgrad with .30 and when the os came up, and you connect it to the internet it should automatically download JB to your device and prompt you to upgrade, this is not happening??
Click to expand...
Click to collapse
No. Every firmware, .26 .30 and JB, would download but fail installation. Now, I'm clicking " check for update" but it says none available
Rooted and back to ICS, but really miss JB too.
buhohitr said:
I will make it work for you. Downgrade back to .30, re root, now here is the trick part, after you root, you should have superuser on your device, open up superuser(keep it open), then download rootcheck from the market to verify that you have root, now download superSU from the market, open it up, it will do the update.Now download Voodoo OTA root keeper, open it up and verify that all the boxes does have check mark to it except one, when you click save button the last box will be checked and now you have the option to "temp" unroot, click on this to save root. Go back to your notification, then click update to JB. Your device will shutdown and do the upgrade. Once it's done, open up OTA root keeper and click restore, bam you have root back.
Click to expand...
Click to collapse
I wanted to thank you. The first tablet overheated and suffered a meltdown. This worked on the replacement.
Thanks a bunch. I have rooted JB now
I bought my S3 used and it was already unlocked but from what I can tell still had the stock ROM (base version says it is I535VRLF2 but DEVICE STATUS says it is modified). When it powers up, I do not get a CWM or TWMP screen -- it goes directly to the normal startup so I am not sure what the previous owner loaded/did. I do not see any folders in the root folder (using ES FIle Explorer) for CWM and nothing in DATA/BACKUP (EDIT: just saw build number is VRALG7)...
Today I got a notice about an OTA upgrade (to HE) and got help on how to freeze it (as I did not want to lose root and all the customization I did to some files) but now I am wondering what changes were made from F2 to HE. I did find a post that talks about the HE upgrade.
Was F2 the previous OTA for the S3, or did my phone miss other OTAs? And if so, I am missing out on some important changes where I should let the OTA happen and then go and unlock the phone again? I read a number of threads about 'the new radio' which I assume is software to improve the phone or WIFI. Am I missing out?
Thanks
Frank
Michigan
I don't think you are missing out on anything to be honest. I did update mine and reroot without any issues, but can't really tell a difference. I would still do it so I can have the latest update on my phone since this one doesn't lock anything that we can't get back into.
Sent from my SCH-I535 using xda premium
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
sfobrien said:
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
Click to expand...
Click to collapse
Thanks for the reply. Will that break either my root or unlock (actually, I am not sure what state this phone is at since I did not do it -- I do find SuperSU in APPS, and have granted SuperUser to programs like Titanium Pro but there is nothing for CWM or other ROM managers...)?
Frank
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
sfobrien said:
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
Click to expand...
Click to collapse
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
FMinMI said:
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
Click to expand...
Click to collapse
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
andimanium said:
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
Click to expand...
Click to collapse
The only way to get stock HE currently is OTA.
sfobrien said:
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
Click to expand...
Click to collapse
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
FMinMI said:
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
Click to expand...
Click to collapse
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
Thanks forgot about GooManager.
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Click to expand...
Click to collapse
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
FMinMI said:
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
Click to expand...
Click to collapse
It is personal choice. I have not had any problems with it and have been running since device was released for pre-order. I run whatever recovery seems to be most stable for the device. CWM for Tbolt. Amon Ra for Rezound. And now TWRP for S3. Have seen more bricks and failed flashes contributed to CWM so I stick with TWRP.
help
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
FMinMI said:
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
Click to expand...
Click to collapse
The OTA installed with a custom recovery installed? Interesting. Usually OTA's fail if anything but stock recovery is installed. I only lost root but restored root with OTA Rootkeeper with stock recovery. Good to know that custom recovery can be installed and still get OTAs!
masonjb said:
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
Boot loader is locked.
Click to expand...
Click to collapse
prdog1 said:
masonjb said:
Boot loader is locked.
Click to expand...
Click to collapse
OK, I used EZ Unlock 1.2 and it said "unlocked" is there a way to know for sure before flashing if it is unlocked?
Thanks!
Click to expand...
Click to collapse
Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.
-lukin- said:
Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.
Click to expand...
Click to collapse
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!
buhohitr said:
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!
Click to expand...
Click to collapse
Thanks. Can't do one firmware upgrade, darn. How many increments are there?
-lukin- said:
Thanks. Can't do one firmware upgrade, darn. How many increments are there?
Click to expand...
Click to collapse
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??
buhohitr said:
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??
Click to expand...
Click to collapse
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.
-lukin- said:
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.
Click to expand...
Click to collapse
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.
buhohitr said:
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.
Click to expand...
Click to collapse
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.
-lukin- said:
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.
Click to expand...
Click to collapse
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Just download them and make sure the final name is dlpkgfile (no extention, exactly like that).
also download command file and the name is command (exactly like that, no extention)
copy them these directories:
command goes to /cache/recovery
dlpkgfile goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-RW-R for both.
This is how it should be after copied:
/cache/recovery/command
/cache/dlpkgfile
power off, then boot into recovery and wait a 10sec it should update. Remember if it failed or boot back into the OS, you need to verify if the two files still there, one of them will be erase and you have to recopy then do it again.
buhohitr said:
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Click to expand...
Click to collapse
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.
-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
The dlpkgfile that updates from ICS to JB is almost 200 MB, the others are around 15 MB each.
buhohitr said:
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.
Click to expand...
Click to collapse
We're in business. I've got ICS, rooted and JB .16 - now working on .18
Thanks for taking the time to help today
P.S. Never forget to unroot! That's how I got here in the first place. Cheers.
Not bad, you're a pretty smart guy after all.
Sent from my ASUS Transformer Pad TF700T using xda premium
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.
BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.