Related
Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!
http://forum.xda-developers.com/showthread.php?t=1996665
cybervibin said:
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Thanks for responding. So if the kernal is a .zip file, I should rename the entire file "boot.img" correct? I don't extact the boot.img file from the zip...
it will be in .img format by default if not try opening it and see!
cybervibin said:
it will be in .img format by default if not try opening it and see!
Click to expand...
Click to collapse
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?
ninjastic said:
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?
Click to expand...
Click to collapse
I was able to figure out that I needed to flash a older RUU to be able to flash a custom rom. :laugh:
ninjastic said:
Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!
Click to expand...
Click to collapse
Did you happen to install an ota update when you still had your stock rom on your phone?
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
ok.... never mind
Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!
It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting
donhashem.dh said:
It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting
Click to expand...
Click to collapse
Thanks for the reply. You are saying to restore my phone using the back up I created using the recovery then reflash?
Or are you saying to download a factory restore and flash that? From what the op states he needed to flash an older build.
---------- Post added at 09:36 PM ---------- Previous post was at 09:03 PM ----------
so I erased my rom, reflashed with the same image and it now boots into the rom. I am seeing a lot of issues though. The android keyboard has FC numerous times. The home button only seems to function one time, it asks which launcher to use, I select on then it will not work as a home button again. Also the button that shows all open application is opening context menus (the ... you see on some apps) instead of showing recent apps I tried reflashing again with the same results. Thoughts/comments?
are u cdma?
EDIT: Issue I has was unrelated to this thread I believe. If anyone else experiences what I described read this post, I outline everything I did and how to fix it (different gapps file )
mrdally204 said:
Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!
Click to expand...
Click to collapse
For anyone else reading this (and thx to donhashem below for elaborating) the stock RUU can be found here. Kudos to all who put these links together :good:
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!
I recently got a htc one m8 that is stuck on the boot screen.
i can get into the bootloader and fastboot seems to work.
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
if i reboot normally it goes back to the bootscreen with the green htc logo.
if i try to go to hboot adb doesn't recognize the device.
so i'm stuck now. i've read several tutorials and tried various things but have no idea where to go from here.
i can tell you that the bootloader says its unlocked and that its set to s-on and there is no os installed.
help
jodahall said:
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
Click to expand...
Click to collapse
Try fastboot erase cache, and flash TWRP again with fastboot.
What is your hboot number, and what TWRP version are you trying?
Also, was your phone recently updated OTA for the Stagefright patch? If so, its a known issue that this recent update does not work with TWRP for some folks.
jodahall said:
if i try to go to hboot adb doesn't recognize the device.
Click to expand...
Click to collapse
This is as it should be. adb doesn't work in hboot. You need to be booted into OS to use adb, possibly will work in recovery (but you can't boot into recovery, so that doesn't really matter).
my hboot version is 3.19.0.0000
i am trying to flash the latest twrp
I have not gotten the ota, this phone has been sitting in a drawer for about 6 months so nothing new has been applied.
I will try erase the cache and reflash the twrp
jodahall said:
i am trying to flash the latest twrp
Click to expand...
Click to collapse
What number TWRP exactly? And you're sure its the TWRP file for the M8, right?
I ask for the number, since I've seen at least a couple times where the person claims they are trying to use the "latest" or "current" TWRP. But when I ask for more info, it turns out the version is not even close to current.
Best to be specific when talking about version numbers.
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
I also tried your advice and from a command window erased the cache and then reflashed. It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Sent from my A0001 using XDA Free mobile app
oh, it worked. I am one step closer as it booted into the custom recovery.....whoohooo
I ran the command "fastboot format cache" from a dos prompt a couple of times, there were errors the first two times, then the 3rd time it created it without error.
ok onto the next steps that are in Vomers guides....
thanks for all your help
jodahall said:
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
Click to expand...
Click to collapse
You are correct, that is latest version (and correct one for the M8). You might re-download just to eliminate the possibility the file wasn't corrupted.
jodahall said:
It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
Click to expand...
Click to collapse
If you are still intending on doing this, don't try any version older than 2.8.4.0 or so. TWRP versions much older than that, won't work on hboot 3.19. TWRP will install and seem to work fine, but after you flash the ROM, the ROM won't boot.
jodahall said:
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Click to expand...
Click to collapse
In the technical sense, the emmc chip does have a finite number of times it can be flashed.
But in reality, I think the number of times the emmc can be flashed before failing is (supposedly) something in the thousands.
Of course, things sometimes fail before they are supposed to, and every extra flash may put you closer to that point (in theory). But I don't let that stop me from flashing what I want, whenever I want to. And flashing recovery a few extra times is not going to hurt anything much IMO.
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
jodahall said:
thanks for all your help
Click to expand...
Click to collapse
There's a button for that!
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
Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
wireaudio said:
Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
Click to expand...
Click to collapse
Are you flashing su2.79sr3 ?
Make sure your using this one. Is the newest
Correct, I am flashing the newest and also tried previous version well, still no go!
wireaudio said:
Correct, I am flashing the newest and also tried previous version well, still no go!
Click to expand...
Click to collapse
Hello,
I'd try reflashing stock boot.img from your 7.1.2 factory image.
The fastboot boot TWRP.img and install TWRP zip.
Install SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Reboot to system. From here you should have superSU​ installed.
Reboot to TWRP and install custom kernel zip.
Hopefully it will work...
Good luck...
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
wireaudio said:
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
Click to expand...
Click to collapse
Hello, it's right here: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
I also see you posting in another thread. I'm going to answer your question here, so all Infos remain in the same place...
wireaudio said:
I basically installed the factory image without the -w flag, turn booted in TWRP (without flashing TWRP) and installed kernel, then flashed super SU then rebooted. Didn't work so I rebooted in TWRP and flashed TWRP and then flashed SuperSU. Note that I had SuperSU installed in 7.1.1 so I assumed it would overwrite. It didn't work so I uninstalled old SuperSU and re-flashed SuperSU 2.79. it still didn't work so I downgraded SuperSU and TWRP one release and reinstalled. Still no go. And that's where I'm at.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
Better question is, how do we select what slot stuff gets installed in? It doesn't seem to be clear, more like a game of chance!
Click to expand...
Click to collapse
Your explanation in the other post and this one are different. Just try in the order from my previous post...
For your information, you can choose the active slot. It's not "like a game of chance". Just use the proper command:
fastboot --set-active=a
Or
fastboot --set-active=b
Good luck...