alright guys got a question. does flashing the stock tar file lock the bootloader??
this file:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
let me know guys thanks!!
my experience
from my experience it doesn't. this thread (step 6) is up to date and says two files need to be flashed in odin to get it completely back to stock and the bootloader locked can someone verify i'm correct? i don't want to mislead anyone:fingers-crossed: http://forum.xda-developers.com/showthread.php?t=1762709
droidrev71 said:
from my experience it doesn't. this thread (step 6) is up to date and says two files need to be flashed in odin to get it completely back to stock and the bootloader locked can someone verify i'm correct? i don't want to mislead anyone:fingers-crossed: http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Yes if you flash a stock image and kernal via Odin you will be back locked up,
Last line of the fore mentioned guide,
Step 10: Reboot! (You should now be booted into factory stock, LOCKED, and bloated ICS 4.0.4)
XRSTOY1 said:
Yes if you flash a stock image and kernal via Odin you will be back locked up,
Last line of the fore mentioned guide,
Step 10: Reboot! (You should now be booted into factory stock, LOCKED, and bloated ICS 4.0.4)
Click to expand...
Click to collapse
What if i just flash the image and not the kernel? (image in photo) it will still lock it right??
luke1333 said:
What if i just flash the image and not the kernel? (image in photo) it will still lock it right??
Click to expand...
Click to collapse
Yes flashing just the stock rom.tar will lock the bootloader...the stock kernel is there to remedy folks who got the verizon screen of death from flashing custom software witb a locked bootloader...it does not take but a extra minute to flash, so you might aswell just flash it to ensure a clean install. Im constantly trying different methods with odin and flashing back to stock. So dont be suprised if my guide is constantly changing. Were still early in development right now. No method is set in stone and things will continue to change.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dear all,
When I try to update the rom I always get these screens. What is going wrong? Ihave unlocked the device, rooted it and then tried to install recovery. Worked once but then I got this error message
That's the stock recovery. Since you unlocked your device, I assume you want to install a custom recovery and then a custom ROM - what exactly were you trying to do?
Note that installing a complete Asus firmware overwrites your custom recovery, so you must reinstall a custom recovery after flashing a complete Asus firmware.
_that said:
That's the stock recovery. Since you unlocked your device, I assume you want to install a custom recovery and then a custom ROM - what exactly were you trying to do?
Note that installing a complete Asus firmware overwrites your custom recovery, so you must reinstall a custom recovery after flashing a complete Asus firmware.
Click to expand...
Click to collapse
I wanted to install cm10 didnt work. Now I can not even update the stock recovery anymore via settings. I am stuck
munsterh said:
I wanted to install cm10 didnt work. Now I can not even update the stock recovery anymore via settings. I am stuck
Click to expand...
Click to collapse
Do you mean "can not even update stock firmware" instead of "recovery"?
Thats OK said:
Do you mean "can not even update stock firmware" instead of "recovery"?
Click to expand...
Click to collapse
yes, thats what i meant. can anybody help?
munsterh said:
yes, thats what i meant. can anybody help?
Click to expand...
Click to collapse
Well we're trying to help!
You need to have a custom recovery such as CWM or TWRP installed.
Otherwise you will always see the stock recovery screen...
Do you know how to get a custom recovery on your tablet?
Have you read any of the stickied posts at the top of the general section?
What is the current state of your device?
Here try the link below. It should install the custom recovery for you. Assuming you have windows it should work. Its a tool I made for my self I hope helps or fixes your problem. This install twrp recovery and is only for Asus TF700t.
Link: http://www.mediafire.com/download.php?liiyrds3si6tmfs
I really need help! I currently have Android 4.4.2 with franco.kernel. I would like to update to Android 4.4.3. So I found the instructions of this type:http://nexus5.wonderhowto.com/how-t...4-4-4-without-losing-any-data-update-0155334/
Everything is OK to a point 6. Shows a console and upload the files but error pops up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I use Nexus Root Toolkit.
How to fix it? NO WIPE of course.
Stop using toolkits. They tend to do more harm than good.
Download the factory images of 4.4.4 and then flash system, radio and boot manually via fastboot. This will bump your android version to 4.4.4 with everything stock.
Hi http://forum.xda-developers.com/showthread.php?p=53178646
Tapatalk-kal küldve az én Nexus 5-el
vin4yak said:
Stop using toolkits. They tend to do more harm than good.
Download the factory images of 4.4.4 and then flash system, radio and boot manually via fastboot. This will bump your android version to 4.4.4 with everything stock.
Click to expand...
Click to collapse
If i have 4.4.2 I can go directly to 4.4.4?
When I flash system and boot manually it does not lose data?
d3zet said:
If i have 4.4.2 I can go directly to 4.4.4?
When I flash system and boot manually it does not lose data?
Click to expand...
Click to collapse
Yes Sir, you can!
Nope, you won't loose any data. Only if you flash the userdata.img will you loose all data from /sdcard.
You could also un-root temporary with OTA RootKeeper to update your system
Since we're all putting our 2 cents in, here's mine
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
rootSU said:
Since we're all putting our 2 cents in, here's mine
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
Click to expand...
Click to collapse
i constantly tell people to do this, its the easiest way out, by far. yet people seemed determined to make it as hard for themselves as possible.
simms22 said:
i constantly tell people to do this, its the easiest way out, by far. yet people seemed determined to make it as hard for themselves as possible.
Click to expand...
Click to collapse
I just copy paste from my clipboard manager, I say it that often
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes, boot recovery, flash, re-flash recovery, re-root
Rooted stock = boot recovery, flash
No brainer really. Flashing an OTA if rooted is a fool's errand
Sent from my Nexus 5 using Tapatalk
I know this might sound dumb to some people, but I am trying to unroot and go back to stock, I have looked at alot of the tutorials on how to revert to stock, I have tried doing a complete unroot in Superuser then putting the 0P6BIMG.zip into my SC Card and letting the bootloader reload it but it ALWAYS come back with root.
Any idea's would be great. Don't have a good reason as to why other than I don't need root and would prefer to get OTAs from Verizon/HTC
Thanks in advance,
Nick
npong said:
I know this might sound dumb to some people, but I am trying to unroot and go back to stock, I have looked at alot of the tutorials on how to revert to stock, I have tried doing a complete unroot in Superuser then putting the 0P6BIMG.zip into my SC Card and letting the bootloader reload it but it ALWAYS come back with root.
Any idea's would be great. Don't have a good reason as to why other than I don't need root and would prefer to get OTAs from Verizon/HTC
Thanks in advance,
Nick
Click to expand...
Click to collapse
If you are talking about my ruu, that will take any future ota updates just fine as long as you 1) don't change any system files and 2) don't flash custom recovery.
Root alone will NOT make you fail otas...not on htc...
dottat said:
If you are talking about my ruu, that will take any future ota updates just fine as long as you 1) don't change any system files and 2) don't flash custom recovery.
Root alone will NOT make you fail otas...not on htc...
Click to expand...
Click to collapse
Okay, I thought I had missed an OTA, but the RUU seemed to be updated to it already. I will post a SS when I get Tapatalk installed
npong said:
Okay, I thought I had missed an OTA, but the RUU seemed to be updated to it already. I will post a SS when I get Tapatalk installed
Click to expand...
Click to collapse
The ruu I have posted is the latest. I didn't bother to make one for the release os version as they had some really annoying bugs (like phones that were stuck in roam from day 1) etc.
Run the ruu and you will update fine whenever they release one. Afterwards you can flash my twrp I have posted in my ruu thread (or recovery of your choosing) and then re flash superuser.zip to reroot .. I suggest using flashify app to backup your stock recovery to your so card after the ruu ..it will let you flash back to stock recovery whenever you need to take an ota
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I have
npong said:
View attachment 2866204Here is what I have
Click to expand...
Click to collapse
As of tonight that's the latest official rom
dottat said:
As of tonight that's the latest official rom
Click to expand...
Click to collapse
Thank you sir.
I got the message thay I can install the update.
When it restarted the phone the installation process was almost on the half bar and suddenly I got a message of Error with the android doll.
Heres a photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh and, I have CF Auto Root and I use only Titanium Backup if that matter.
You must be 100% stock, unrooted to accept the update.
fastboot flash stock system.img then re-root.
rootSU said:
You must be 100% stock, unrooted to accept the update.
fastboot flash stock system.img then re-root.
Click to expand...
Click to collapse
What? that doesn't gonna solve my problem because I'm not gonna flash a system again and lose my data.
Thats an headache for me.
Many people have this problem, Read here:
https://productforums.google.com/fo...-up-and-personalizing-your-device/33D4982KnyA
Even unrooted stock devices. And I'm 100% stock rooted.
With fastboot flash system.img you don't lose anything of your data, only root.
digitLIX said:
What? that doesn't gonna solve my problem because I'm not gonna flash a system again and lose my data.
Thats an headache for me.
Many people have this problem, Read here:
https://productforums.google.com/fo...-up-and-personalizing-your-device/33D4982KnyA
Even unrooted stock devices. And I'm 100% stock rooted.
Click to expand...
Click to collapse
Then flash a custom 5.0.1 rom with a custom recovery or you can never update BTW the update from 4.4.4 to 5.0(.1) is quite big so a full wipe after the flash is required or you`ll have fc`s all over the board.
digitLIX said:
What? that doesn't gonna solve my problem because I'm not gonna flash a system again and lose my data.
Thats an headache for me.
Many people have this problem, Read here:
https://productforums.google.com/fo...-up-and-personalizing-your-device/33D4982KnyA
Even unrooted stock devices. And I'm 100% stock rooted.
Click to expand...
Click to collapse
I suppose you're not really familiar with this. Your data is not stored in /system. fastboot flashing a system.img only installs to /system. Only fastboot flashing userdata.img would overwrite your data, which you may note that I did not advise you to do.
Have a read of the "adb and fastboot" thread in General > Sticky roll-up
rootSU said:
I suppose you're not really familiar with this. Your data is not stored in /system. fastboot flashing a system.img only installs to /system. Only fastboot flashing userdata.img would overwrite your data, which you may note that I did not advise you to do.
Have a read of the "adb and fastboot" thread in General > Sticky roll-up
Click to expand...
Click to collapse
Sorry for the confusion, I will try it and i will update you very soon.
Best of luck
Hello,
I had lollipop image before (rooted shieldtablet), then i upgraded it to marshmallow by using "cm-13.0-20161101-NIGHTLY.shieldtablet.zip" also added GAPPS (google apps) i did this all from the recovery mode, mount image etc... and then the problems started.
I couldn't get the tablet to run the ROM so i had to upgrade the bootloader i think it was...
Now im trying to upgrade the CM to the latest version but it doesnt go further than about 20 seconds when installing the new version then it stops, the Android icon stops spinning its"heart"... see picture below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done this all directly with the tablet, downloaded the ROM and so on and installed from the recovery mode/ ...mount.... not by PC.
Please help me?! how can i make the bootmenu to work again?? step by step....
Best way to do this to be able to upgrade my ROM further.
(first time i upgraded the root by myself):crying::crying:
Thanks in advance,
Gabriel
First tell us, step by step, exactly what you did to get to this point.
you tried to update with the original recovery?
lafester said:
First tell us, step by step, exactly what you did to get to this point.
Click to expand...
Click to collapse
I tried to install the new cwm from november this year, so I downloaded it from xda forum and then I followed the steps, flush some stuff and then install the cwm image.
So when it stopped halfway I thought that it stopped working and that made me reboot the tablet and I reinstalled the rom but It happened again. I read on the site it said that it could take up to 10 minutes until late it's done so that's why I let it just be and after it was successful and also installed the gapps that was sucessful aswell. So I rebooted the tablet and started the rom but It didn't work. I read that I had to update the recovery so I did and all worked well but when I try to go into the recovery to do anything after the update of recovery it stops working after 20 seconds...
wiQbold said:
you tried to update with the original recovery?
Click to expand...
Click to collapse
No I don't think so, I just used the compatible recovery for the latest rom cause it didn't work with my old recovery before. As I mentioned on the reply.
Do you think I should reinstall the recovery and can I do it through the PC? ?
Help please
Help please!
g4brie1y said:
I tried to install the new cwm from november this year, so I downloaded it from xda forum and then I followed the steps, flush some stuff and then install the cwm image.
Click to expand...
Click to collapse
Your description is not detailed enough to get an idea what your problem actually is.
For now. Find TWRP for shieldtablet 3.0.2-2 is the latest I think.
go in bootloader (fastboot) mode and open a shell
fastboot flash recovery twrp*
go to recovery mode
install rom.
Cwm? from here?
you can also if nothing will work flash a original recovery image.