Hey, noob question, but I'm somewhat new to nexus devices and I love them. I have a lot of experience flashing with my GS4 but not nexus devices. Is there any way to accept an OTA update on my nexus 7 flo after flashing custom recovery? What about just root with stock recovery? Thanks for any help
You are in the wrong section...
OTA-Updates works well with TWRP... But if OTA Update fails I would prefere simply to flash the system.img +boot img from the factory Image...
If you are on 4.2.2 or older you can root with Motochopper.
For 4.3 or older you need a custom Recovery (wich will be overwritten on OTA Update) or an unlocked bootloader. Via an unlocked Bootloader you can simply boot CF-Auto-Root via fastboot boot, without flashing anything...
TheScarySnail said:
Hey, noob question, but I'm somewhat new to nexus devices and I love them. I have a lot of experience flashing with my GS4 but not nexus devices. Is there any way to accept an OTA update on my nexus 7 flo after flashing custom recovery? What about just root with stock recovery? Thanks for any help
Click to expand...
Click to collapse
You can not get ota updates once you flash custom recovery but there is a way to have root and use recovery without ever flashing it.
If you boot into the bootloader and then download the TWRP latest image for the Flo, you can boot into the recovery straight from your computer's hard drive.
Code:
fastboot boot recovery path/to/recovery.img
Will boot into recovery from your computer instead of flashing it. Theoretically, if you do this every time, then you should be able to have whatever you want to flash on your device, but still accept ota updates.
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"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"
}
Just got my N7 yesterday, what does Flo mean? Sorry for the noob question
Sent from my LG-D800 using XDA Premium 4 mobile app
uly609 said:
Just got my N7 yesterday, what does Flo mean? Sorry for the noob question
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flo refers to the Nexus 7 2013 Wi-Fi-only version, while Deb refers to the LTE Nexus 7 2013.
Related
When i go to restire a backup it runs for 4 seconds and says successful...but no backup is actually restored anf if i reboot ill get black screen due to lack of rom...
how can i restore a backup?
Sent from my GT-N7000 using Tapatalk 2
Look in your backup folder...what files do you see?
Here is what I see... in twrp/0000000000
{
"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"
}
sent from a kindle fire on cm 9
Hmm. That should restore. Have you tried reinstalling TWRP or changing versions?
How do I change versions without use of a computer?
sent from a kindle fire on cm 9
Here's one way
http://forum.xda-developers.com/showpost.php?p=22608974
Is there a way to make a zip or something of the recovery files to flasg? I don't really want touse smirkit
Sent from my GT-N7000 using Tapatalk 2
Is there a reason you don't want to use smirkit?
I am constantly flashing roms... Isnt it true that smirkit goes away after i flash a new rim? Will i still get to keep the updated twrp? Thanks for your help
Sent from my GT-N7000 using Tapatalk 2
asf58967 said:
I am constantly flashing roms... Isnt it true that smirkit goes away after i flash a new rim? Will i still get to keep the updated twrp? Thanks for your help
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yes and yes. Smirkis has significantly updated his script since the last time I used it. It used to be a set of scripts to be run individually to install whatever image or binary you needed. Now, you flash the smirkit.zip installer in recovery along with any files it comes with. This makes it much easier to launch and less likely to encounter any errors, but the overall result of running the script is still the same. The image or binary gets flashed to its respective partition, to stay.
Since the smirkit.zip is flashed to the system partition in recovery, flashing a new ROM, simply overwrites the system partition along with the Smirkit installer.
So yes, you can use Smirkit and not worry about losing TRWP after rebooting or flashing a new ROM.
Smirk it saved the day. Thank you so much for your help
sent from a kindle fire on cm 9
Hi! I am stuck on flashing insecure boot image via ODIN. Already 10minutes gone. I get this window for such a long time already ((
{
"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"
}
What should i do now?
P.S. I was trying to load TWRP via ODIN on stock firmware. It was flashed. But when i was entering recovery, i was getting stock recovery from samsung. So i decided that recovery is locked somehow and i need to load insecure boot first. Am i right?
Melodycd said:
Hi! I am stuck on flashing insecure boot image via ODIN. Already 10minutes gone. I get this window for such a long time already ((
What should i do now?
P.S. I was trying to load TWRP via ODIN on stock firmware. It was flashed. But when i was entering recovery, i was getting stock recovery from samsung. So i decided that recovery is locked somehow and i need to load insecure boot first. Am i right?
Click to expand...
Click to collapse
First I'm thinking your going to need to root your device. Start HERE:
http://forum.xda-developers.com/showthread.php?p=33854391
Yes you can load TWRP onto your firmware with Odin. Hopefully that was a tar file you were using!! Because if not that's why it didn't work for you!
I only really use Odin if I run into a BIG problem or need too return to fully stock firmware!!
Since it didn't work right with Odin.
After you root your device then all you'll need to do is install goo manager, install open recovery from there done.
TWRP found HERE :
http://forum.xda-developers.com/showthread.php?p=33867032
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
TWRP needs root...or it won't persist after boot ..
Run CF auto root....
Allow the device to boot itself ...
Then power down and enter download mode and flash your custom recovery ....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
guys please help. i rooted my phone using this http://forum.xda-developers.com/showthread.php?t=2181103 then installed rom manager from google play store and installed CWM then when i tried to boot into recovery a bunch of errors came like gapps has stopped and all, then it proceeded to reboot. however when powering on, i was met with this error
Secure booting Error!
Cause: boot certification verify
im getting this error always now and cant use my phone. pls advise on what to do. simple procedures will help alot. TIA
There is a thread for unbricking the phone. You could try the solutions outlined there.
Sent from my LG-E975 using Tapatalk 4
roycejp said:
There is a thread for unbricking the phone. You could try the solutions outlined there.
Sent from my LG-E975 using Tapatalk 4
Click to expand...
Click to collapse
thank you. now the 2nd question is how to prevent this error. unsecure bootloader?
I don't have the answer to your 2nd query. I haven't yet attempted to root my phone.
I can only suggest to try again after unbricking, or use a different rooting method...
I'll leave this question to more experienced people here.
Sent from my LG-E975 using Tapatalk 4
roycejp said:
There is a thread for unbricking the phone. You could try the solutions outlined there.
Sent from my LG-E975 using Tapatalk 4
Click to expand...
Click to collapse
roycejp said:
I don't have the answer to your 2nd query. I haven't yet attempted to root my phone.
I can only suggest to try again after unbricking, or use a different rooting method...
Sent from my LG-E975 using Tapatalk 4
Click to expand...
Click to collapse
I already posted an inquiry to another thread. hopefully there is a simple way to load an unsecure bootloader, or a simple guide.
{
"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"
}
Have you unlocked the bootloader after rooting?i know,stupid question from me,but i have to be sure. Of course you unlocked the bootloader,because otherwise root is pretty useless,since you can't flash cwm and uninstall some system apps without having those issues you mentioned.
Sent from LG E975 pwd by CM 10.2/smart phones,dumb people.
I have a Tmobile LTE Deb, it has 4.4, rooted with TWRP recovery. I received 4.4.2 OTA tonight, clicked reboot and upgrade, it went to TWRP but failed to upgrade, it went so quick, I couldn't see an error, I don't know where the OTA was downloaded to. So I downloaded 4.4.2 zip for LTE upgrade from the thread here, when I tried to flash it from TWRP, I received this weird error "This package is for DEB devices, this device is a FLO". I downloaded again, reinstall, same error. My device is a deb as you can see from the attachment. Any suggestions?
Thanks in advance.
{
"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"
}
Sent from my Nexus 7 using xda app-developers app
Maybe it's the download for 4.4.2 from 4.4.1, and you still have 4.4. You can download the KRT16S to KOT49H or go from KRT16S to KOT49E then KOT49E to KOT49H. Go here
http://www.ibtimes.co.uk/articles/5...013-android442-kot49h-bugfix-install-root.htm
Sent from my Nexus 7
gemstocks said:
I have a Tmobile LTE Deb, it has 4.4, rooted with TWRP recovery. I received 4.4.2 OTA tonight, clicked reboot and upgrade, it went to TWRP but failed to upgrade, it went so quick, I couldn't see an error, I don't know where the OTA was downloaded to. So I downloaded 4.4.2 zip for LTE upgrade from the thread here, when I tried to flash it from TWRP, I received this weird error "This package is for DEB devices, this device is a FLO". I downloaded again, reinstall, same error. My device is a deb as you can see from the attachment. Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
You're probably using a recovery made for flo. Download the one for deb and you should be good to go.
You're right on. Somehow the root toolkit flashed wrong TWRP. I flashed TWRP for Deb and it is good to go. Thanks a bunch!
meekrawb said:
You're probably using a recovery made for flo. Download the one for deb and you should be good to go.
Click to expand...
Click to collapse
I just upgrade the s3 from 4.1.1 to 4.4.2 and now sais SYSTEM UNCONSISTENT and all apps are crashing, what can I do. I dont want to loose my data
Thank
Alfred1516 said:
I just upgrade the s3 from 4.1.1 to 4.4.2 and now sais SYSTEM UNCONSISTENT and all apps are crashing, what can I do. I dont want to loose my data
Thank
Click to expand...
Click to collapse
Did you try to root or flash a zip? How did you attempt to upgrade to 4.4.2? Did you ODIN or flash the zip?
Just tried to update with the original Sammobile firmware
Sent from my SGH-T999 using XDA Free mobile app
-facepalm-
Sent from my SPH-L710 using Tapatalk
Alfred1516 said:
Just tried to update with the original Sammobile firmware
Sent from my SGH-T999 using XDA Free mobile app
Click to expand...
Click to collapse
Pretty sure you flashed the wrong thing if you got it from here, this is the Sprint forum, and judging by your signature you have the TMo variant... and now you're probably screwed because you can't downgrade your firmware. Read read read, and don't flash stuff that's not for your phone.
{
"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"
}
bilgerryan said:
Pretty sure you flashed the wrong thing if you got it from here, this is the Sprint forum, and judging by your signature you have the TMo variant... and now you're probably screwed because you can't downgrade your firmware. Read read read, and don't flash stuff that's not for your phone.
Click to expand...
Click to collapse
could he not go into download mode and try to flash his stock rom?
Trozzul said:
could he not go into download mode and try to flash his stock rom?
Click to expand...
Click to collapse
No because he flashed the 4.4 Bootloader and they don't have 4.4 yet, so flashing the 4.3 firmware will brick it... He should be able to Odin a recovery and wipe everything and flash a new ROM.