Database Users

[Q] I cant update, goes into restart loop!

I am trying to solve for weeks, tried a lot of roms but still could not manage.
My phone is huawei u8800. Kernel 2.6.32.9
buildnumber u8800v100r001c00b138sp04
It is 2.2.2
I click online upgrade in about phone menu but it cant find anything to upgrade.
I install cwm and flashing a new rom, for example b518 2.3 but after installing, it restarts after loading logo and this goes on. And everything is wiped, cwm is wiped after this and i have to go into android recovery to solve this. I reset wipe data and if i am lucky, i can open phone in 2.2.2. If not, it makes me to try to go back to.
I dont know how this happened first. I was using aurora then i wanted to go back to stock rom. I made also partition and maybe this is the reason.
In cwm, it cant mount ext sd so i have to + - and power to upgrade.
Please help me to solve this. I tried a lot of things but couldnot manage.

Anyone helps? I am waiting helps, thank you

OK. I just recently got stuck in the same situation and this is how I solved it:
1. Download and install official B517: http://www.mediafire.com/download/vh3aqdx5608ubb8/U8800V100R001C00B517G001+%28Beta1.0%29%28Overseas+Normal%29%28Gingerbread%29.zip
2. After installing, if it boots then that is good, but if it doesn't boot then it still doesn't matter. Mine didn't boot, so I went into pink screen by turning off the phone, and then pressing vol +, vol -, and power at the same time to go into pink screen.
3. When you go into pink screen, connect your phone to Windows PC (Windows 7 or 8 should work).
4. Download cwm recovery 6.0.2.8: https://code.google.com/p/forumber-projects-for-u8800/downloads/detail?name=recovery-clockwork-6.0.2.8-2.6.35.7-u8800.img&can=2&q=
5. When you connect pink screen phone to computer, a removable disk will come up. Go into the removable disk and you will see recovery.img there. Now, rename the cwm recovery you downloaded above to recovery.img (if you cannot see .img at the end then just type recovery). After renaming to recovery.img, copy the downloaded cwm recovery.img to the removable disk, and replace the old recovery.img in the removable disk.
6. After replacing stock recovery.img with cwm recovery.img, you will have CWM Recovery 6.0.2.8. Now, you can go into recovery to install a ROM. Make sure you install Aurora 5.0 experimental first.
I have tried to keep the steps simple. If you follow them you should be fine. If you don't understand anything then please ask and I will try to reply. I cannot reply right now because it is time for me to sleep, so you will have to wait

rqmok said:
OK. I just recently got stuck in the same situation and this is how I solved it:
1. Download and install official B517: http://www.mediafire.com/download/vh3aqdx5608ubb8/U8800V100R001C00B517G001+%28Beta1.0%29%28Overseas+Normal%29%28Gingerbread%29.zip
2. After installing, if it boots then that is good, but if it doesn't boot then it still doesn't matter. Mine didn't boot, so I went into pink screen by turning off the phone, and then pressing vol +, vol -, and power at the same time to go into pink screen.
3. When you go into pink screen, connect your phone to Windows PC (Windows 7 or 8 should work).
4. Download cwm recovery 6.0.2.8: https://code.google.com/p/forumber-projects-for-u8800/downloads/detail?name=recovery-clockwork-6.0.2.8-2.6.35.7-u8800.img&can=2&q=
5. When you connect pink screen phone to computer, a removable disk will come up. Go into the removable disk and you will see recovery.img there. Now, rename the cwm recovery you downloaded above to recovery.img (if you cannot see .img at the end then just type recovery). After renaming to recovery.img, copy the downloaded cwm recovery.img to the removable disk, and replace the old recovery.img in the removable disk.
6. After replacing stock recovery.img with cwm recovery.img, you will have CWM Recovery 6.0.2.8. Now, you can go into recovery to install a ROM. Make sure you install Aurora 5.0 experimental first.
I have tried to keep the steps simple. If you follow them you should be fine. If you don't understand anything then please ask and I will try to reply. I cannot reply right now because it is time for me to sleep, so you will have to wait
Click to expand...
Click to collapse
Thanks the issue is thatin pink screen my computer doesnot show partitions. Sometimes it shows but not after an unsuccessful installation rom. I dont know when it shows. Shouldş i use adb shell or something to change recovery? Or ubuntu?_

I wrote alot of things but icant see them. Maybe deleted.
http://forum.xda-developers.com/showthread.php?t=2295318 i nstalled this after making parttion zip wjhic i found, you posted .I first intalled 1, then without wpiping final then v3e the lastest. But when i click power off, it shows powering off but wwaiting.
How i solved my big problem, i did not wait to go into android recovery(wiping cwm) after bootnig, immediately pulledo ut battery and then instaleld on it Thank you rqmok, you are great helpful nice person.

How will i understand if i did partiton correct? In storage
int storagae
total space 1.48 gb
apps 40 mb
availabe 1.38 gb
usb storage total space 14 gb
(this isext)
usb storage again
total space 1.02 gb
and availabele 1.02 gb
It means int sd card 1.02 gb and phone memory 1.48 gb? How can i move these applications 44 mb to ext sd, with app2sd?

Cursed Chico said:
How will i understand if i did partiton correct? In storage
int storagae
total space 1.48 gb
apps 40 mb
availabe 1.38 gb
usb storage total space 14 gb
(this isext)
usb storage again
total space 1.02 gb
and availabele 1.02 gb
It means int sd card 1.02 gb and phone memory 1.48 gb? How can i move these applications 44 mb to ext sd, with app2sd?
Click to expand...
Click to collapse
You cannot see the system size from the android settings. Besides that, I don't know how to see if system is partition.
The partition you have posted is data partition (the top one), and the bottom one is your internal sdcard. From that, all I can see is that you have data partition, and not system partition.
I guess the only way of finding out if you have system partition is to flash a big ROM. If the ROM starts up fine then you don't need system partition, but if the ROM doesn't start up then you need system partition.
By the way, what ROM do you have now? Does your phone work fine?

rqmok said:
You cannot see the system size from the android settings. Besides that, I don't know how to see if system is partition.
The partition you have posted is data partition (the top one), and the bottom one is your internal sdcard. From that, all I can see is that you have data partition, and not system partition.
I guess the only way of finding out if you have system partition is to flash a big ROM. If the ROM starts up fine then you don't need system partition, but if the ROM doesn't start up then you need system partition.
By the way, what ROM do you have now? Does your phone work fine?
Click to expand...
Click to collapse
I dont want to go into that loops again so it is ok if partition is not correct.
I aM Using aurrasp final v3ce. I did not use so much but it seems fine.I will use a long time again. Now i am trying to restore my bakcups.Thank you again

OS wiped accidentally from TWRP recovery

I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk

Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?

Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk

Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs

Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk

The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.

Fastboot flash system system.img
?

removed

I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?

Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.

5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.

The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.

pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.

I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks

Create Stock Recovery.img from FTF File

Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!

tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.

So my only way is to flash via Flashtool without wipe?

tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.

fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.

realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?

So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?

tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.

XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.

tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)

Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.

realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!

tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.

Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.

realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!

Accidentally wiped system

So I was going to install xXx NoLimits rom and I went to wipe my storage as to not cause and errors or mess ups. I went to select cache and dalvik/art in advanced wipe and accidentally hit system and swiped to format. Now I'm here in twrp with nothing but the root directory.
I have already tried adb sideload to get OOS back on it. It completed but nothing shows up under sdcard or in any of the root folders. I also tried adb push to the sdcard and it spits out and error. I looked back at some old forum posts and they said to install the sdcard fix in twrp but how am I supposed to get in on the phone if sideload or push don't work?
EDIT: I do have backups of OOS but have no way to get them on the phone.

I can get stuff on the phone now with push and sideload but when I sideloaded the OOS zip and tried installing it, TWRP says its corrupt! Its goes up to about 40% in powershell but the bar on TWRP says 100% and it stops the sideload command from completing. after it "finishes" powershell says "Total xfer: 1.00x"

You still can get into TWRP correct? Then once in TWRP connect your phone to your PC. Take the full zip, not the OTA and drag it into the phone and flash the full OTA. You shouldn't have to worry about sideloading with ADB. I've done this plenty of times, and one by accident as well.

Eric214 said:
You still can get into TWRP correct? Then once in TWRP connect your phone to your PC. Take the full zip, not the OTA and drag it into the phone and flash the full OTA. You shouldn't have to worry about sideloading with ADB. I've done this plenty of times, and one by accident as well.
Click to expand...
Click to collapse
It's okay I figured it out. The problem was is that I completely formatted the system partition and couldn't directly access it from my computer. My solution was to ADB push the full zip file and wait for it to finish. Then I could flash it in TWRP. This whole thing could have been made a whole lot simpler if the Team Win devs would put out 3.1.1-2 and just use the OTG capability of the unofficial one.

Wiping system is no big deal. Just flash the rom zip file and you'll be good.

PwnedBySumo said:
It's okay I figured it out. The problem was is that I completely formatted the system partition and couldn't directly access it from my computer. My solution was to ADB push the full zip file and wait for it to finish. Then I could flash it in TWRP. This whole thing could have been made a whole lot simpler if the Team Win devs would put out 3.1.1-2 and just use the OTG capability of the unofficial one.
Click to expand...
Click to collapse
Or if OnePlus added sd card reader into phone...
This is a valid argument for it...

I had your own problem, I solved buying an OTG cable and then I flashed the rom.zip from TWRP.

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.

Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.

v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?

Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img

v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.

You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.

Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk

v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.

SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.

Do I need to suck it up and redo the whole phone again........ :/