Need some help with my new Nexus 7 - Nexus 7 (2013) Q&A

I just got a new Nexus 7 today and naturally, my first goal is to unlock and root.
I started by booting into the bootloader and doing "Fastboot oem unlock"
I said yes, wipe and it said it worked fine.
After that I installed the latest TWRP for the Nexus 7 2013
It installed just fine and i installed supersu 1.69 through it
for some reason it is stuck at the boot animation now and in TWRP it says 0 internal storage space and fails whenever i factory reset.
what can I do to fix this?

fenguepay said:
After that I installed the latest TWRP for the Nexus 7 2013
It installed just fine and i installed supersu 1.69 through it
for some reason it is stuck at the boot animation now and in TWRP it says 0 internal storage space and fails whenever i factory reset.
what can I do to fix this?
Click to expand...
Click to collapse
Did you try installing TWRP again?

meekrawb said:
Did you try installing TWRP again?
Click to expand...
Click to collapse
yes and i also tried installing cwm recovery too. no luck with either. im currently trying to reboot after re-unlocking.

fenguepay said:
yes and i also tried installing cwm recovery too. no luck with either. im currently trying to reboot after re-unlocking.
Click to expand...
Click to collapse
Wiping data doesn't work?
You MAY have to flash back to stock and start over.
Other people have had this problem, check here:
http://forum.xda-developers.com/showthread.php?t=2380913
Keep in mind that that thread is from before Google released the factory images. Hopefully it can help you out though.

You can also try one of scrosler's pre-rooted stock ROMs. I'd recommend using fastboot to wipe cache, system and userdata to be on the safe side.
http://www.scottsroms.com/downloads.php?do=cat&id=94

http://forum.xda-developers.com/showthread.php?t=2381582 fixed it

Related

help android 4.3 stuck at google screen

Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.
Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.
oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes
FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!

[Q] boot loop

Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
DarkGruf said:
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
Click to expand...
Click to collapse
No idea anyone ? Could it be hardware related for instance ?
Wipe system, data, cache, dalvik cache and internal. Then flash factory image.
h4xx0rr said:
Wipe system, data, cache, dalvik cache and internal. Then flash factory image.
Click to expand...
Click to collapse
I did, about 5 or 6 times and still in boot loop.
ty
DarkGruf said:
Hello,
My son's gn is catched in a boot loop : google then X then google and so on
I wiped (factory reset) No result
I can access to recovery so i flashed 4.3 (JWR66Y) google factory image here : https://developers.google.com/android/nexus/images?hl=FR. The flash is completed but still catched in a boot loop.
I can even flash a custom recovery and all goes well i can perform anything in recovery mode but i'm still in the boot loop
when i restart the phone.
Any idea ?
Thanks in advance.
Click to expand...
Click to collapse
What caused this ? Did you flash a ROM or something ?
Bootloader is unlocked (padlock symbol visible) right? If you've previously locked it, then Recovery won't do anything if you haven't unlocked.
FredFS456 said:
Bootloader is unlocked (padlock symbol visible) right? If you've previously locked it, then Recovery won't do anything if you haven't unlocked.
Click to expand...
Click to collapse
Yes it's unlocked, I can even flash a custom recovery.
Atishay Jain said:
What caused this ? Did you flash a ROM or something ?
Click to expand...
Click to collapse
It's my son's device so i don't know really but I'mquite sure he did not flash anything. I do it for him when he needs.So no, I have no idea. One minute before it was working one minut after it reboot itself and stays in boot loop.
DarkGruf said:
It's my son's device so i don't know really but I'mquite sure he did not flash anything. I do it for him when he needs.So no, I have no idea. One minute before it was working one minut after it reboot itself and stays in boot loop.
Click to expand...
Click to collapse
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Atishay Jain said:
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Click to expand...
Click to collapse
What is v6 supercharger???
h4xx0rr said:
What is v6 supercharger???
Click to expand...
Click to collapse
Its a script to improve performance. Anyways u seem to be unaware of that so it means you've not done anything like installing a MOD, Try updating the recovery.
Can you give me link for supercharger?
Atishay Jain said:
Was there any mod installed (something that u flashed to make the phone faster) like the v6 supercharger or any other mod ?
Also I think that you should try updating your recovery and then flashing a rom onto your device. I think CM is available for your device (which I assume to be a nexus as you have mentioned the nexus system images page in the OP). Search the xda threads for a ROM and try flashing it.
Click to expand...
Click to collapse
No, I did not intall any mod, last rom i had on it was a modaco but when I gave thephone to my son I just pushed the last stock root rom i picked from xda 4.2 I think. Still I goona try what u sayed, I did not try to push a custom rom only google images. TY, I will tell what happens. And yes it's an European Samsung Galaxy Nexus as we are in Galaxy nexus section
h4xx0rr said:
Can you give me link for supercharger?
Click to expand...
Click to collapse
Here you go :
http://forum.xda-developers.com/showthread.php?t=2733251
There are also a few other tricks and MODs listed there if u want to improve your phone's performance.
Rate the thread well if it helped you.:good:
Looks allot like my girlfriends phone and this thread http://forum.xda-developers.com/galaxy-nexus/help/normal-boot-loop-problem-t2875961
factory reset does not do/wipe anything, pushed files don't stay on the device after reboot, flashing new rom from PC does not stick
Nexus seems to be in some kind of readonly mode.

[Q] Very strange recovery issue

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

Bootloop after flashing TWRP, CM13

I'm (or rather, was) on CM13 nightly, today I downloaded TWRP through Flashify and flashed it, previously I was using Philz Touch, now I have a bootloop. I just had a bootloop a few days ago and had to install everything over again, and I really don't feel like doing it again. What can I do?
Error503 said:
I'm (or rather, was) on CM13 nightly, today I downloaded TWRP through Flashify and flashed it, previously I was using Philz Touch, now I have a bootloop. I just had a bootloop a few days ago and had to install everything over again, and I really don't feel like doing it again. What can I do?
Click to expand...
Click to collapse
Can you enter the recovery mode? And if so I would recommend reflashing everything, that usually helps xD
Summoned Egar said:
Can you enter the recovery mode? And if so I would recommend reflashing everything, that usually helps xD
Click to expand...
Click to collapse
Yes I can, but I reeeeeally don't feel like going back to stock AGAIN, I was thinking maybe flashing CyanogenMod Recovery would help fix the issue since TWRP is apparently not compatible with Marshmallow, the problem is I can't get my PC to recognize my phone in fastboot mode therefore I can't flash the new recovery. Any ideas?
Error503 said:
Yes I can, but I reeeeeally don't feel like going back to stock AGAIN, I was thinking maybe flashing CyanogenMod Recovery would help fix the issue since TWRP is apparently not compatible with Marshmallow, the problem is I can't get my PC to recognize my phone in fastboot mode therefore I can't flash the new recovery. Any ideas?
Click to expand...
Click to collapse
Why didn't you backup your data? Always backup your data! Moreover, put the image to flash on your sd card
Summoned Egar said:
Why didn't you backup your data? Always backup your data! Moreover, put the image to flash on your sd card
Click to expand...
Click to collapse
Alright, I can do that. How do I flash it after it's on my SD?
Error503 said:
Alright, I can do that. How do I flash it after it's on my SD?
Click to expand...
Click to collapse
Wipe as usual, then in TWRP go to mount and choose external_sd, after that navigate up until you find the folder external_sd and load from there
You don't need to go back to stock. If you can enter recovery, you can wipe system (only) and dirty flash your cm13 over it. It usually works and dont lose your personal files nor installed apps. If it don't, do a full wipe and flash your rom again.

TWRP bootloops

I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices

Categories

Resources