Develop Bugs

AOSP 2.99 beta5 (five) Reboot loop! bricked

The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you

Go back to stock and start fresh.
Sent from my i9250

bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..

Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here

ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.

Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out

khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again

altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck

still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you

Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?

ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol

Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!

ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.

Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck

ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.

ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.

1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .

Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck

It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

trying to flash twrp; it just hangs!

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,

I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....

mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.

mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?

XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!

mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.

XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again

mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??

mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!

XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..

mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.

XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!

mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.

@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!

Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk

freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

I destroyed my phone

I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
 @xunholyx

Try to RMA

zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Badger50 said:
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Even if pay for fix, it is acceptable. It is a fact that I do wrong thing, and I am willing to pay for it.
But if can find a easy way except RMA is better.
Overall, please some advice about how to solve this. Thanks.

Does anyone know if qualcomm flash can flash image without oem unlocking?

zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.

v12xke said:
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.
Click to expand...
Click to collapse
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.?

zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.

v12xke said:
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.[/QUOTE
Sounds about right fasboot twrp . That has saved many phones.
If you can't figure out what to do pay a Dev to use TeamViewer to help you out.
I did that 5 years ago until I understood
ADB commands
Click to expand...
Click to collapse

boot, set active, flash, flashing of fastboot all don't work, because bootloader is locked.

Just reread your post. You can save you phone. You need latest platform tools from Google. Then 8.1 ota image from Google. Learn fastboot commands.
When people start to jump ahead and push,click,touch things they shouldn't you end up here.
Fyi all files for easy reference should be in the plat-forms tools folder.
Download them now.
So let's start:
Fastboot --set-active=_a will set to "a" partition, usually not bootable
Fastboot --set-active=_b will set to "b" partition, usually bootable
Try this:
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_a
On phone scroll to recovery factory reset
Then
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_b
On phone scroll to recovery factory reset
If USB debugging wasn't turned on, boot to recovery and and side load 8.1 ota.
Follow instructions in recovery side load menu
I think it's "adb sideload filename.ota.zip"
Factory reset after boot
Or just get platform tools and 8.0/8.1 imagine depends on what you are on and restore. Probably won't work since OEM/debugging not switched on.
If you get it up and running unlock the phone to help you in the future. Yes both OEM and critical.
Good luck

matt1313 said:
Just reread your post...
Click to expand...
Click to collapse
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.

v12xke said:
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.
Click to expand...
Click to collapse
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.

matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..

[email protected] said:
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..
Click to expand...
Click to collapse
Why can't you get to recovery? Stock recovery?
If so sideload ota

matt1313 said:
Why can't you get to recovery? Stock recovery?
If so sideload ota
Click to expand...
Click to collapse
Stock.. Because all possible accessing process to recovery ending with " Can't find valid operating system. The device will not restart". Same issue with sideload ota.. "Flashing is not allowed in lock state"... I have not felt so helpless for a long time.. What a chance..

matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
The only thing that matters is that the bootloader is locked (no fastboot is possible) and no recovery mode (no adb is possible). Done. OP is from China where there is no RMA, so he is "extra" S.O.L. I recognize you are wanting to help, but those are the facts.

I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?

Wait until just after Christmas, then contact Google and say you got it as a present and it says no operating system when it turns on. They're RMA it.

matt1313 said:
I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?
Click to expand...
Click to collapse
As I said, phone is booting only one screen that says "Can't find valid operating system. The device will not restart"..

unlock_critical

flashed
fastboot flashing unlock
then
fastboot flashing unlock_critical
now the phone wont boot just staying on google boot screen
flashed ota img still no joy any ideas thanks

jaythenut said:
flashed
fastboot flashing unlock
then
fastboot flashing unlock_critical
now the phone wont boot just staying on google boot screen
flashed ota img still no joy any ideas thanks
Click to expand...
Click to collapse
You'd be better off flashing the factory image vs the ota. Did you side load it, or try fastboot??

Badger50 said:
You'd be better off flashing the factory image vs the ota. Did you side load it, or try fastboot??
Click to expand...
Click to collapse
i fastbooted it fastboot -w update image-taimen-opd1.170816.025.zip when it reboots i get google splash its like theres no software on the phone just tried flashing 8.0 still no joy
geting this as well telling me the device is corrupted

jaythenut said:
i fastbooted it fastboot -w update image-taimen-opd1.170816.025.zip when it reboots i get google splash its like theres no software on the phone just tried flashing 8.0 still no joy
Click to expand...
Click to collapse
So you tried fastbooting the ota??? That's not gonna work. You need to download the factory image, then unzip/extract it and put all the contents in your SDK platform-tools file. Then edit and save the flash-all.bat script with the -w removed, then you should be fine :good:

Badger50 said:
So you tried fastbooting the ota??? That's not gonna work. You need to download the factory image, then unzip/extract it and put all the contents in your SDK platform-tools file. Then edit and save the flash-all.bat script with the -w removed, then you should be fine :good:
Click to expand...
Click to collapse
yeah that what ive been doing ive installed twrp and there is no img on the phone just flashed system .img on its own still nothing

jaythenut said:
yeah that what ive been doing ive installed twrp and there is no img on the phone just flashed system .img on its own still nothing
Click to expand...
Click to collapse
The factory image# you posted earlier, ending in .025, is the November build. Is that what your wanting to do??? What build were you on before you started this??

Badger50 said:
The factory image# you posted earlier, ending in .025, is the November build. Is that what your wanting to do??? What build were you on before you started this??
Click to expand...
Click to collapse
was on 8.1 dec went to flash 8.1 jan couldnt flash as i didnt unlock critical so unlocked it and thats when this all started read on here some guy flashed back to 8.0 and it fixed it but not me lol

jaythenut said:
was on 8.1 dec went to flash 8.1 jan couldnt flash as i didnt unlock critical so unlocked it and thats when this all started read on here some guy flashed back to 8.0 and it fixed it but not me lol
Click to expand...
Click to collapse
Ah, now I see. In order to downgrade, you have to let your phone get wiped. So put the -w back in the flash-all script.
However, since your phone has already been wiped with unlocking_critical, might as well just flash the January update and don't edit the flash-all script. Then let your phone boot up, do a minimal setup, then go back to fastboot mode and boot twrp, then root if you want to with magisk 15.2 :good:

Badger50 said:
Ah, now I see. In order to downgrade, you have to let your phone get wiped. So put the -w back in the flash-all script.
However, since your phone has already been wiped with unlocking_critical, might as well just flash the January update and don't edit the flash-all script. Then let your phone boot up, do a minimal setup, then go back to fastboot mode and boot twrp, then root if you want to with magisk 15.2 :good:
Click to expand...
Click to collapse
cant find valid operating system the device will not start
wtf ive flashed 10 times today haha

jaythenut said:
cant find valid operating system the device will not start
wtf ive flashed 10 times today haha
Click to expand...
Click to collapse
Is your SDK up to date, as are you device drivers?? Also, what transfer cable are you using?? Your using up all my options bro!

Badger50 said:
Is your SDK up to date, as are you device drivers?? Also, what transfer cable are you using?? Your using up all my options bro!
Click to expand...
Click to collapse
yeah im out of ideas as well but thanks for trying to help :good:
just sideloaded ota looks like that worked

jaythenut said:
yeah im out of ideas as well but thanks for trying to help :good:
just sideloaded ota looks like that worked
Click to expand...
Click to collapse
I hate being defeated!!!! If everything is up to date, then the only other thing I could suggest is to go into stock recovery, do a factory reset, then start over. There is also a rescue script put there if that doesn't work. I'll find the link if you need it.

Badger50 said:
I hate being defeated!!!! If everything is up to date, then the only other thing I could suggest is to go into stock recovery, do a factory reset, then start over. There is also a rescue script put there if that doesn't work. I'll find the link if you need it.
Click to expand...
Click to collapse
all fixed with ota :fingers-crossed:

jaythenut said:
all fixed with ota :fingers-crossed:
Click to expand...
Click to collapse
You gotta be sh****ng me! Well good for you dude. Did you side load it?

Badger50 said:
You gotta be sh****ng me! Well good for you dude. Did you side load it?
Click to expand...
Click to collapse
Yeah sideloaded it strange that that worked but like you out of ideas so thought I'd try and boom

jaythenut said:
Yeah sideloaded it strange that that worked but like you out of ideas so thought I'd try and boom
Click to expand...
Click to collapse
Well, I'll be damned! Oh well, I learned something new at least. Glad you got it working though :good:

[ROM] H932 Oreo v20k - stock - keeps TWRP

This is ONLY for the H932. There are no ASSERT checks, so you better pay attention. If you flash this on any other model, you will brick your phone.
Also, I was in a hurry so there is no progress indicator. Just let it flash, you will know when it is done -- it doesn't take THAT long.
So you have used lafsploit and would like to have Oreo back -- got ya covered.
Flash this zip: link in TWRP.
Code:
SHA256: [B]931f3b424c8d5af3bb6b88863fc8659fa9c4ffef87f53b3eb3f33d4670debd58[/B]
You can dirty flash it over 10d.
It is 100% stock. The only change I made was removing recovery-from-boot.p, but it appears that isnt enough to keep recovery from getting wiped if you dont flash Magisk.
After flashing this, you MUST flash Magisk again or you will lose TWRP and root, and have to use lafsploit all over again.
-- Brian

Ignore

I downloaded the zip went to twrp tried to flash got error 6 trying to flash so I wiped all partitions including system now I lost twrp and can't even get to download mode only getting fastboot mode with 2 options restart or power off I'm assuming I lost download mode. Lol any suggestions on how to get download mode @ Brian or anyone who can help? Haha thanks appreciate the help and support!?

Fix uploaded.
-- Brian

Excellent work good sir. Now just have to hope some ROM devs start supporting the H932 variant.

tattedup said:
I downloaded the zip went to twrp tried to flash got error 6 trying to flash so I wiped all partitions including system now I lost twrp and can't even get to download mode only getting fastboot mode with 2 options restart or power off I'm assuming I lost download mode. Lol any suggestions on how to get download mode @ Brian or anyone who can help? Haha thanks appreciate the help and support![emoji106]
Click to expand...
Click to collapse
Have you tried both options to get into DL mode? With hardware keys and power off vol up and plug in?
Sent from my [device_name] using XDA-Developers Legacy app

Sooo I flashed the zip, now trying to get back into recovery mode and it just says "No Command" on the screen when doing adb reboot recovery.

Josh McGrath said:
Have you tried both options to get into DL mode? With hardware keys and power off vol up and plug in?
Click to expand...
Click to collapse
Haha!! I'm a noob!! Lol I kept doing vol down!! ?? Thanks bro!??

tattedup said:
Haha!! I'm a noob!! Lol I kept doing vol down!! [emoji106][emoji106] Thanks bro![emoji23][emoji23]
Click to expand...
Click to collapse
Glad you're not bricked . We all start somewhere.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
Josh McGrath said:
Glad you're not bricked . We all start somewhere.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
When you download the file, what's the file name? Is a bunch of random letters and in bin format? I may have issues going on here
Sent from my [device_name] using XDA-Developers Legacy app

Josh McGrath said:
Glad you're not bricked . We all start somewhere.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
When you download the file, what's the file name? I may have issues going on here
Click to expand...
Click to collapse
H93220k.zip
But I think Brian uploaded a fix for it

Fixed

Josh McGrath said:
Thanks for that. Hmm I definitely have something going on then. This is my file name after it downloads
1XAfpo2cZvdZrPICeYg_UIvA0oeE0V1ux.bin but it has a meta folder so it's a zip for sure but I bet it's getting corrupted on the download.
Click to expand...
Click to collapse
Have you tried a different browser? I had an issue similar a bit ago(not related to this file), where the file was downloading as a bin. I tried a different browser and no cognito mode and it fixed it for me.

Cleaned

Well, I did it to myself. I was in a hurry and wiped everything and installed the Oreo zip, booted up without flashing magisk zip and stock recovery came back and I haven't had time to start from step 1.
Don't do what I did, FLASH MAGISK after the oreo :doh
I just re-read the OP and I don't know what I did that caused TWRP to go bye bye but stock recovery absolutely came back.
Thanks for doing all this for us. I literally have nothing right now to give, but I will be donating in the next week or so.

@Josh McGrath Weird. I wasnt able to test the zip since i boxed up the V30 that i was loaned to make this happen. I have double checked that i removed recovery-from-boot.p .. there must be another mechanism in place that restores stock recovery. I will update the first post so people know that flashing Magisk is NOT optional.
Sorry you have to go through the process all over again.
-- Brian

Believe I nuked LAF, download mode acts like it is booting up, freezes with the little logo then reboots to system, not able to use LG up at all due to not going in to download mode, tried using lg bridge to fix recovery(refreshing latest firmware thinking it would maybe help rejuvenate LAF)
Couldn't get fastboot to work at the beginning, but ended up being able to relock the bootloader
were the mess up was I believe, thinking h933 LAF was still installed and rerooting.
Anyway to flash LAF thru FWUL?

wills3gslide said:
Believe I nuked LAF, download mode acts like it is booting up, freezes with the little logo then reboots to system, not able to use LG up at all due to not going in to download mode, tried using lg bridge to fix recovery(refreshing latest firmware thinking it would maybe help rejuvenate LAF)
Couldn't get fastboot to work at the beginning, but ended up being able to relock the bootloader
were the mess up was I believe, thinking h933 LAF was still installed and rerooting.
Anyway to flash LAF thru FWUL?
Click to expand...
Click to collapse
I hate to be the bearer of bad news too. But I don't have a download mode anymore either.. can't even boot into it. Tried it with just plugging it in as well. Doesn't exist.
Also don't have TWRP because I didn't flash Magisck after.

ClockworkImpulse said:
I hate to be the bearer of bad news too. But I don't have a download mode anymore either.. can't even boot into it. Tried it with just plugging it in as well. Doesn't exist.
Also don't have TWRP because I didn't flash Magisck after.
Click to expand...
Click to collapse
If I remember correctly I flashed majisk after flashing 20k.zip, wish I would of waited to update but at least others will be aware.
Still great job @runningnak3d, might wanna pull the 20k.zip for now, seems there is another check for lafbak to overwrite LAF corrupting the partition

wills3gslide said:
Believe I nuked LAF, download mode acts like it is booting up, freezes with the little logo then reboots to system, not able to use LG up at all due to not going in to download mode, tried using lg bridge to fix recovery(refreshing latest firmware thinking it would maybe help rejuvenate LAF)
Couldn't get fastboot to work at the beginning, but ended up being able to relock the bootloader
were the mess up was I believe, thinking h933 LAF was still installed and rerooting.
Anyway to flash LAF thru FWUL?
Click to expand...
Click to collapse
So you have twrp installed still?
Sent from my [device_name] using XDA-Developers Legacy app

Josh McGrath said:
So you have twrp installed still?
Click to expand...
Click to collapse
It put stock recovery back on