I just picked up 6p yesterday .and using wug tools kit to unlock ,root and flashed recovery and custom rom.
Everything seem is fine ,but every time when I try boot into twrp recovery or reboot device ,I got waring page .
Is it normal ?
Sent from my Nexus 6P using XDA-Developers mobile app
yijinsa said:
I just picked up 6p yesterday .and using wug tools kit to unlock ,root and flashed recovery and custom rom.
Everything seem is fine ,but every time when I try boot into twrp recovery or reboot device ,I got waring page .
Is it normal ?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah we all got that
yijinsa said:
I just picked up 6p yesterday .and using wug tools kit to unlock ,root and flashed recovery and custom rom.
Everything seem is fine ,but every time when I try boot into twrp recovery or reboot device ,I got waring page .
Is it normal ?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Perfectly normal. It happens when you unlock the bootloader.
Related
Hi
I am on stock 4.1.2 unlocked and rooted and I was on TWRP recovery then I changed to CWM 6.0.1.0 because there are some problems in it an yesterday I flash the new TWRP 2.3.1.0 with goo manager and rebooted to TWRP and I did a backup of the rom and rebooted the tablet and I trasfer the paranoidandroid rom to my SD card and open the goo manager and select reboot recovery , it didn't reboot to recovery i I don't know why I did it a couple of times the tablet just rebooted normally like there are no recovery and I go to flash the CWM 6.0.1.0 and it is the same the phone rebooted normally it didn't rebooted to recovery
Somebody help me please
Sent from my Nexus 7 using xda app-developers app
Anybody
Sent from my Nexus 7 using xda app-developers app
You should be able to use fastboot to flash a recovery img or use a toolkit.
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
You should be able to use fastboot to flash a recovery img or use a toolkit.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I did but it is the same it is reboot normally
Sent from my Nexus 7 using xda app-developers app
sharjackmission said:
I did but it is the same it is reboot normally
Click to expand...
Click to collapse
Did you remember to change the recovery-from-boot.p file after you did the 4.1.2 update?
iElvis said:
Did you remember to change the recovery-from-boot.p file after you did the 4.1.2 update?
Click to expand...
Click to collapse
Yes after I update to 4.1.2 OTA those problems came
And now I managed to reboot to CWM by wug's toolkit but I can't enter to recovery from the bootloader
Sent from my Nexus 7 using xda app-developers app
sharjackmission said:
Yes after I update to 4.1.2 OTA those problems came
And now I managed to reboot to CWM by wug's toolkit but I can't enter to recovery from the bootloader
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is a problem many Nexus 7 owners are experiencing since the 4.1.2 update, whether by OTA or flashed from sd card. There apparently is an issue with the bootloader (version 3.43). One solution that I have seen on t his forum and on another is to flash the last version of bootloader (3.31 I think). I have tried every conceivable method to get into either stock recovery or custom recovery to no avail...flash, 2 different toolkits, ROM Manager, TWRP...you name it, I've tried it to no avail. I have not tried to flash back to the old bootloader though...just doesn't sound like a good idea...although I have not heard of problems being encountered by those who have flashed the old bootloader...yet. There are a couple thread in this sub forum on the subject if you want to read the 100 different ways users have tried to get a recovery.
jpcalhoun said:
This is a problem many Nexus 7 owners are experiencing since the 4.1.2 update, whether by OTA or flashed from sd card. There apparently is an issue with the bootloader (version 3.43). One solution that I have seen on t his forum and on another is to flash the last version of bootloader (3.31 I think). I have tried every conceivable method to get into either stock recovery or custom recovery to no avail...flash, 2 different toolkits, ROM Manager, TWRP...you name it, I've tried it to no avail. I have not tried to flash back to the old bootloader though...just doesn't sound like a good idea...although I have not heard of problems being encountered by those who have flashed the old bootloader...yet. There are a couple thread in this sub forum on the subject if you want to read the 100 different ways users have tried to get a recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32918876
I found this and I didn't tried it because it may not work see for your self
I just wondering when the android 4.2 will be released to solve all those problems
Sent from my Nexus 7 using xda app-developers app
I think my bootloader is 3.41 and I have no issues but I flashed the factory image from Google because my touchscreen didn't respond after the 4.1.2 OTA.
Try flash the bootloader and see if it works and if not then flash the factory image.
Just note that if you use the script/batch file to flash it all automagically it will wipe your SD so flash each image separately and don't flash userdata.img
flashing factory fixes any software problem, its the best thing about owning a nexus.
Sent from my Nexus 7 using xda premium
found it
if you are on the latest bootloader vesion
reboot to booloader
fastboot erase cache
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot
thank you all
Ok every guide I looked at said you can easily flash something to gain root again well in order to flash anything you have to have root so it doesn't make any sense and I didn't see any guides on this or related posts and I'm running 4.2.2
Sent from my Nexus 7 using xda app-developers app
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
boot into recovery
flash the supersu.zip root package.
What is so complicated about that?
you dont need root to flash something, you need an unlocked bootloader and a custom recovery.....
i swear the word root has lost all meaning these days. everyone wants it, but it seems so very few actually understand what it is.
Pretty sure you just need to fastboot flash a custom recovery, then you can flash the superuser binaries by chainsdd (Google the package), then install superuser or superSU from the market.
Not familiar with nexus 7, but this is how I rooted a galaxy nexus. There should be a sticky in your device specific forum with links to the process and files.
From my Evo LTE, yup.
I went to fastboot but when I go into recovery I get an error
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
I went to fastboot but when I go into recovery I get an error
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
An error?
if you want help, provide info
I'm in the car ATM but when I turn my device off and I go into boot loader I push either up or down like 2 times it shows recovery mode I click it and it shows a android guy with a red thing in the center of him
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
I'm in the car ATM but when I turn my device off and I go into boot loader I push either up or down like 2 times it shows recovery mode I click it and it shows a android guy with a red thing in the center of him
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
thats stock recovery.....did you ever FLASH a custom recovery, like all the guides tell you to?
I tried downloading clockworkmod recovery from ROM manager but the download failed so I downloaded recovery manager from the play store and downloaded a recovery using the app it said the recovery installed
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
I tried downloading clockworkmod recovery from ROM manager but the download failed so I downloaded recovery manager from the play store and downloaded a recovery using the app it said the recovery installed
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Dude,
As the guides tell you, and I lined out above, you need to FASTBOOT FLASH RECOVERY
unless you are already rooted, then downloading ROM Manager or 'recovery manager' from the app store doesnt do any good....
you need a computer to do this in fastboot mode.
Damn I was hoping I could avoid using my friends very slow comp lol
Sent from my Nexus 7 using xda app-developers app
I'm in the similar situation - I upgraded rooted 4.2.1 via modified OTA (original OTA was failing because of one apk) and now I have 4.2.2, but even though I had SuperSU which was ticked to "survival mode" (should keep the root), it apparently didn't. I don't have TWRP anymore, when I press power+vol dn I get the standard "start" screen (original recovery). Also, when I turn N7 on, it is displaying keychain that is OPEN, that means my bootloader is unlocked?
So my question(s)... my bootloader is probably unlocked? If I do the steps:
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
boot into recovery
flash the supersu.zip root package
will I loose all data/apps? I ask because when I first rooted with toolkit, I lost all apps/data.
Also, where to find supersu.zip ? That is different to the installed SuperSU.apk, right?
Damn I can't make ADB work... I tried 2 computers.... Damn google for making this so [email protected]#[email protected]$ .... Constant problems, nothing else. Any clues? I ofcourse, tried kill-server and start-server, no matter what my device is showing offline....
Just checked with my phone (SGNII) and it is working just fine... no clue why Nexus is showing as offline..
I flashed the clockworkmod touch zip from my recovery.
It didn't give me the touch recovery, I thought "whatever" and booted back into my rom.
It wouldn't boot.
I went back into recovery and flashed PA rom and gapps.
They weren't booting, I decided to give them a few minutes.
It finally booted.
It no longer connects to wifi or tmobile.
I can't transfer files over usb.
Wugfresh's toolkit couldnt return it to stock.
I thought the recovery might have gotten messed up when I tried to flash CWM touch, so I flashed TWRP from Wugfresh's toolkit.
I used adb sideload to flash a stock rooted rom.
It still took forever to boot, and is still not connecting to wifi/network.
TL;DR I can boot into fastboot and recovery and even the rom but I have no network connection... help guys :'(
It says BASEBAND VERSION - N/A... could that be the problem? If so, how do I fix it?
This is why we don't use toolkits. Return to stock using ADB and do it again...
Sent from my Nexus 4 using xda premium
When I try to fastboot flash the stock image it says "does not contain recovery.sig" "does not contain boot.sig" and only updates the bootloader.
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
ethan.r.besbris said:
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup.. this one https://developers.google.com/android/nexus/images#occam
So I just flashed the radio by itself and its working fine now thanks for your help man.
No problem. Glad you're up and working.
Sent from my Nexus 4 using xda premium
*****
i had twrp recovery but since i had problems and had to flash stock i needed to root and install costume recovery...
ive rooted my device but suddenly the methods i used before to install twrp dosent work
tried via ROM maneger..tried using TWRP maneger up and treid flashing .img file using rasher(and now when I reboot to recovery i get an error)
btw i want twrp becuse ive saved a backup i did using it and i dont know how to do it without having TWRP
Use AutoRec. Why were you using methods that weren't tested/recommended?
Sent from my LG-D800 using XDA Free mobile app
penser said:
Use AutoRec. Why were you using methods that weren't tested/recommended?
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
they were recommended...anyway thaks used autorec worked fine
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
A bad flash, perhaps? Have you checked the MD5 after downloading?
Possible bad download but at this point I can't reflash the recovery until I can fast boot .. I gotta order another Type C to USB to connect the phone to the computer for fast boot grrrrr...
Thx
Sent from my Nexus 6P using Tapatalk
Glad to help! Next time make sure you check MD5 before flashing (even then an occasional bad flash could still cause trouble, but hey, what's the choice here?) You can still boot to Android normally, no?
Sidenote: anyone knows if a micro B to C adaptor would work with fastboot?
Yeah I can still boot to Android fine jus when I select recovery n bootloader it hangs in bootloader. I have to hard reset to get out of bootloader mode lol....
Jus sucks BC now I gotta wait until friday to order a Type C to USB cable to use the computer to fast boot TWRP to recovery.. :/
I jus got this 6P 4 days ago coming from the HTC M9 Developer Edition I decided to go with the 6P over the M10 even though I would have gotten $100 off the M10 for not using my UhOh protection.
But I'm currently Stock w/ root until I figure out or understand this whole Vender thing when flashing Roms.. Jus being very cautious.
With HTC you jus flash the ROM you want but here some say jus flash the ROM and some say flash the Vender matching the ROM.. Lol,..
Sent from my Nexus 6P using Tapatalk
About the vendor img... Not too sure about the whole technical details behind them, but I just flash them every time Google updates them (think monthly security updates), at the very least to get rid of the 'vendor img outdated' popup. You don't need to flash a new vendor img everytime you update/switch ROMs, but only when there's a new vendor.
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
scoot0073 said:
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
People have been facing the same issue all around. Even I did, last night after updating to N Preview. Anyhow, the only solution I know right now is to have a decrypted filesystem (disable encryption), for TWRP to boot and work properly.
Yeah disable encryption I believe I read requires booting into recovery and wiping User Data or something alone those line's.
Unless there's a option in Android settings to disable it idk yet as I jus had the phone a few day's.
But so far I happy with my decision to get the 6P over the M10 even if the 6P is 4 or 5 moths old...
Sent from my Nexus 6P using Tapatalk
OK I got the latest TWRP Recovery flash . I used Flashify app and it flashed the recovery and I got a working recovery now..
Sent from my Nexus 6P using Tapatalk
Pain-N-Panic said:
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank u so much that fixed my borked recovery thank you again
Sent from my Nexus 6P using Tapatalk