i have tried to install twrp on my 5x, 6, and 6p, with the same results "do loop". doing a twrp backup of the stock rom doesn't work as flashing it results in the same "do loop". is there a good "how to" on backing up my stock rom to my pc without twrp? i have lineage 15.1 on my 6p but doing the twrp format cleans all.
I don't see the point of backing up stock rom in first place, and I don't really know what's your problem, explain... more precisely. Your twrp can't stick in stock rom, or phone bootloop after restoring backup? Answering last question: you can get factory system image right from google's servers.
i had trouble flashing the stock rom, i keep getting errors, i thought if i saved the one on the phone to my pc i might have a better chance at restoring it. installing twrp resulted in the stock rom either doing a twrp reboot or forever hung on the google logo. when i flashed lineage it starts to load but boots back to twrp. i got it to install on my 6p after wipe and format. i will try that on the 5x, will it work? just looking for a fall back position.
dr1445 said:
i had trouble flashing the stock rom, i keep getting errors, i thought if i saved the one on the phone to my pc i might have a better chance at restoring it. installing twrp resulted in the stock rom either doing a twrp reboot or forever hung on the google logo. when i flashed lineage it starts to load but boots back to twrp. i got it to install on my 6p after wipe and format. i will try that on the 5x, will it work? just looking for a fall back position.
Click to expand...
Click to collapse
Just curious what type of "errors" you are having with flashing the stock ROM? Is it possible you need to download a newer version of fastboot/adb?
@73 the old memory is not that great but i seem to recall format error. when i got the phone from ebay i did the full stock setup up to the latest 8.1. i recorded that info and that was my first google firmware flash with no joy. i had to go back to android 6 before i found one that would flash. i am running linux xubuntu, which i keep updated.
If the stock image won't flash using fastboot or OTA, it seems like your phone is faulty.
nowster said:
If the stock image won't flash using fastboot or OTA, it seems like your phone is faulty.
Click to expand...
Click to collapse
as noted in my last post, it finally did flash after trying several versions. i am hardly any kind of expert on the subject, but there seems to be problem with the twrp software on the nexus 5x and i add the 6p where the same deal occurs.
dr1445 said:
as noted in my last post, it finally did flash after trying several versions. i am hardly any kind of expert on the subject, but there seems to be problem with the twrp software on the nexus 5x and i add the 6p where the same deal occurs.
Click to expand...
Click to collapse
Why are you trying to use TWRP to flash the stock ROM (granted, I've seen the option to flash ".img" files but never used for anything other than "boot.img"). You should be using a pc and "fastboot".
For flashing stock you should be using fastboot, or the stock recovery and an OTA image.
Related
I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2
Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.
where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.
Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
eNVy said:
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
Click to expand...
Click to collapse
post a screenshot from cmd here to see the error you get from fastboot...
kopfik said:
post a screenshot from cmd here to see the error you get from fastboot...
Click to expand...
Click to collapse
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
eNVy said:
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
Click to expand...
Click to collapse
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Shouldn't you be using the latest twrp 2.8.7.2? Ive had issues flashing roms without using the latest version. You could also have issues with older versions of twrp and encryption. Id suggest wiping data from twrp and then flashing the factory image from bootloader.
Sent from my Nexus 5X using Tapatalk
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
I think to be able to really do anything you need to get into bootloader and have fastboot recognize the device. Make sure the files from 6.01 are all correct and you're flashing in the right order. Follow the guide item #8 http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 If you can get the system.img and vendor.img flashed and then lock the bootloader it will wipe everything to factory, internal storage included. If you do that you must have stock recovery.img flashed as well. If downloading system.img hangs reboot and try it again.
kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Sorry, I was using v.2.8.7.2.
mnehring said:
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
Click to expand...
Click to collapse
I got it to work. I just had to change the USB port.
Why don't you try a different USB port or a different cable. Or even try on a different computer.
Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
Hey guys,
I have a Nexus 7 that is stock and on 4.4.2. When I bought it all I did was run Towel root to get root and I have not taken an update in all these years. I also installed an app to unlock bootloader. I am even still on stock recovery.
I'd like to go to 7.1 now. What is the easiest way for me to do this right now? Please include all steps as I do not have a ton of experience with this.
Thanks in advance!
I apologize if I maybe my question was too broad. Can i go directly from 4.4.2 to 7.1 or do I have to upgrade to something else first.
Can i leave the tablet rooted with towel root or do I have to unroot first?
Thanks
http://forum.xda-developers.com/showthread.php?t=2382051
You should read and watch some basics to understand what
you have to do.
In short: unlock bootloader, flash latest factory image or latest bootloader and radio, flash twrp and then 7.1 rom of your choice
Thanks for the link, I appreciate it.
I'd like to try and just go straight from 4.4.2 to 7.1 if that is possible. I now went ahead and installed TWRP on the tablet. This went fine and TWRP seems to be working perfectly.
So now I have unlocked bootloader, SU working, TWRP and I'm still on 4.4.2. What is now the easiest way for me to get 7.1?
^He was just saying you need the latest bootloader. To get that you can flash the latest factory image or just the bootloader.img itself (and radio if you have the mobile version). Latest is 4.08
Either way download the latest factory image and on your tablet download the rom and gapps you wan't. We can only fit the smaller gapps read about it in your roms thread.
I'm assuming you're familiar with fastboot, if not there are many, many guides all over xda and the internet.
Drag and drop the bootloader.img in the factory zip into your fastboot folder and with the tablet booted to the bootloader run this:
Code:
fastboot flash bootloader bootloaderfilename.img
fastboot reboot-bootloader
The file name for flo is bootloader-flo-flo-04.08.img
(your kitkat rom will most likely not boot with the newer bootloader but you don't need to)
Use the volume buttons to select recovery and press power to boot twrp.
Now just wipe the tablet (not internal storage) and flash the rom and gapps. That's it. Reboot.
Ok, i really appreciate your help folks. I think im getting closer to understanding what I need to do.
Yosmokinman, where can i get the 4.08 bootloader img?
Also, you mentioned radio if I have the mobile version. What do you mean by this? My tablet is wifi only?
When i flash the rom and gapps do i do that from twrp? Can i flash both at same time one after the other or do i have to do something in between?
When i reboot will i have to reinstall all my apps, photos, files, etc. Or will they still be there?
Sorry for all the questions, Im hoping to not make any mistakes. I love my little Nexus and dont want to hurt it :good: thanks very much once again!
yosmokinman said:
^He was just saying you need the latest bootloader. To get that you can flash the latest factory image or just the bootloader.img itself (and radio if you have the mobile version). Latest is 4.08
Either way download the latest factory image and on your tablet download the rom and gapps you wan't. We can only fit the smaller gapps read about it in your roms thread.
I'm assuming you're familiar with fastboot, if not there are many, many guides all over xda and the internet.
Drag and drop the bootloader.img in the factory zip into your fastboot folder and with the tablet booted to the bootloader run this:
Code:
fastboot flash bootloader bootloaderfilename.img
fastboot reboot-bootloader
The file name for flo is bootloader-flo-flo-04.08.img
(your kitkat rom will most likely not boot with the newer bootloader but you don't need to)
Use the volume buttons to select recovery and press power to boot twrp.
Now just wipe the tablet (not internal storage) and flash the rom and gapps. That's it. Reboot.
Click to expand...
Click to collapse
^ Factory Images for Nexus and Pixel Devices
wifi only N7 is not the mobile version so forget about the radio. You're looking for "razor" on the images page.
Yes the wiping and rom/gapps flashing is done through twrp and you should be flashing rom then gapps one after the other then hit reboot.
Everything will be gone but your internal storage. You'll have to redownload and setup everything. Don't worry about hurting the tablet you can recover from pretty much any problem with the factory image.
yosmokinman, ok I am getting ready to do this! Thank you again.
So I found the 4.08 bootloader thanks to your link. I think I am just going to go with latest Cyanogenmod 7.1 snapshot. If I understand correctly I will be using opengapps ARM 7.1 Pico.
Does above seem correct?
Also, what about my kernel, I am still on the stock/original kernel (I believe 3.4.0-gac9222c#1) from back when I originally got the tablet new. Does that just stay the same?
Finally, you mentioned that as long as I have a factory image I should be good if I run into any problems. Do you mean a factory image that I can download (from where?)? or do you mean an actual image from my tablet? As of now I have never made an image of mine (not sure how I would do that).
I can almost taste that Nougat now
Thanks again!
treepog said:
yosmokinman, ok I am getting ready to do this! Thank you again.
So I found the 4.08 bootloader thanks to your link. I think I am just going to go with latest Cyanogenmod 7.1 snapshot. If I understand correctly I will be using opengapps ARM 7.1 Pico.
Does above seem correct?
Also, what about my kernel, I am still on the stock/original kernel (I believe 3.4.0-gac9222c#1) from back when I originally got the tablet new. Does that just stay the same?
Finally, you mentioned that as long as I have a factory image I should be good if I run into any problems. Do you mean a factory image that I can download (from where?)? or do you mean an actual image from my tablet? As of now I have never made an image of mine (not sure how I would do that).
I can almost taste that Nougat now
Thanks again!
Click to expand...
Click to collapse
When you flash the ROM, you'll get a new kernel. All of that is wiped when you wipe system from TWRP. Then when you flash the ROM from TWRP, you'll get a new system and the kernel and all else.
Sound fine. Except there is no nougat snapshot (thats cm13 marshmallow) you wan't Cyanogenmod 14.1 nightly.
If you downloaded the latest image for razor from that link above that is the factory image. If you look in the zip there is another zip that has the different partition images.
You said your N7 is the wifi only version so make sure the bootloaders file name is "bootloader-flo-flo-04.08.img" don't flash the wrong one.
Ok, thanks again. I will report back once I do it. Thank you so much!
Ok, I finally had a chance to do this today. I decided to go with CM android 6 instead of 7 because I really want something that is totally stable. When I got the factory image I saw it only goes up to android 6 and since I was getting the bootloader from 6 (4.08 bootloader) I figured just stick with 6.
If I wanted to upgrade to CM 7 or 7.1 would the 4.08 bootloader still be correct??
Anyway, it is like I have a brand new tablet. Running great!
THANKS SO MUCH FOR THE HELP!!!
I'm running stock MM with the Nova launcher. Aside from the intermittent sensor issues, it's still a remarkably smooth tablet.