On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Just to add, I'm getting the message "no OS installed" when trying to reboot in recovery.
ul49 said:
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Click to expand...
Click to collapse
Did you flash the boot.img first, then the ROM?
Can you wipe System?
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
ul49 said:
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
Click to expand...
Click to collapse
The boot.img has the kernel in it. If you didn't flash the CM10.zip you have no operating system.
Wipe System, and Factory Reset
Flash boot.img
Flash the CM10.zip, flash google apps, and you should be good after that
Now flash the rom zip from recovery (twrp)
Sent from a slithery smooth phone!
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
no,you flash the boot.img in fastboot, and then you flash the rom.zip and gapps.zip from recovery (twrp)
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
No, do a clean wipe.
boot your phone into fastboot
download the fastboot files http://www.mediafire.com/?4dx982z93w8z7wk and extract them to your desktop
on your computer, open up cmd and type
cd desktop
cd foldername (the folder that has fastboot.exe)
fastboot flash boot boot.img
reboot into recovery
flash CM10, flash gapps, reboot
I see. The problem is that I seem to be unable to mount my phone and sd card through recovery.
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
ul49 said:
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
Click to expand...
Click to collapse
I think you are typing the command wrong
./adb push file /destination
or ./adb push cm10.zip /mnt/sdcard
./adb push cm10.zip /sdcard
whatever the mount point is for the sdcard
Tried that too. It just reloads the opening adb dialogue.
ul49 said:
Tried that too. It just reloads the opening adb dialogue.
Click to expand...
Click to collapse
does ./adb devices return your phone as connected?
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
ul49 said:
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
Click to expand...
Click to collapse
I'm not familiar with OS X and android, are there any specific drivers you may need to install?
Are you in your bootloader or recovery?
All necessary drivers were installed. The device was being recognized before, but for some reason isn't now. I'm stuck on the "This build is for development purposes only" screen now since I can't get into recovery or bootloader using adb now since the device isn't recognized...
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
ul49 said:
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
Click to expand...
Click to collapse
because it is probably at /mnt/sdcard
Successfully pushed the files. Of course, I've hit another problem. Trying to install the ROM through TWRP and it's failing. Same with Gapps. I'm seeing "unable to mount /sdcard" and unable to mount storage. I've already cleared cache, wiped system, factory reset/
Related
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
therion0 said:
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
Click to expand...
Click to collapse
CWM cant mount SD you need TWRP for that and a RUU put you back to stock but the bootloader needs relocking. So did you even try booting the rom because the red writing is fine.
you didn't mention it, but you should wipe system and caches as well as data
Not hard brick. you can chose the correct Ruu file and flash it to your phone.... solved your case.
Darknites said:
CWM cant mount SD you need TWRP for that
Click to expand...
Click to collapse
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
touch of jobo said:
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
Click to expand...
Click to collapse
Oh right seems a lot work lol, I think I stick to TWRP.
Darknites said:
Oh right seems a lot work lol, I think I stick to TWRP.
Click to expand...
Click to collapse
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
shadowch31 said:
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
Click to expand...
Click to collapse
Habit and guides.
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
rugmankc said:
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
Click to expand...
Click to collapse
I not seen updates but then I not looked and I didn't move over in till it got the usb mount.
when i run the CMD Command prompt adb reboot bootloader I get error: device not found, i was able to flash the boot.img and i got the 2 OKs but i get that error now... what now?
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
therion0 said:
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
Click to expand...
Click to collapse
You lost SD then and best off running a RUU to recover it.
ok i'm lost.. how do i run an RUU to recover it?
therion0 said:
ok i'm lost.. how do i run an RUU to recover it?
Click to expand...
Click to collapse
Download the right RUU for your carrier and location by looking at http://forum.xda-developers.com/showthread.php?t=1543588 and you can get free download at http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
Then plug in your phone and follow the instructions when you run the RUU .exe file.
AKToronto
but everytime i try to run it, it says it fails because the phone it is not connected to the computer but it is...
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
rugmankc said:
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
Click to expand...
Click to collapse
Ya he messed it up so needs RUU. He has PM me just waiting on a reply.
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Akkordinator said:
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Click to expand...
Click to collapse
TWRP has ADB Sideload feature. Means you can flash zips using adb. Of course you can flash a roms this but keep in mind you have to flash the kernel (boot.img) manually immediately after flashing the rom.zip. When flashed Rom.zip by using ADB sideload method make SURE that you direct go into fastboot mode and flash the kernel (fastboot flash boot boot.img) (you can extract the boot.img from your rom.zip)
May be a compatible rom this time? But you're lucky -> Infact you already deleted everything you won't have to perform a wipe before flashing lol
LS.xD said:
Of course you can flash a roms
Click to expand...
Click to collapse
Ok, but I dont know with which command (fastboot flash what? or adb?)
You can use adb sideload as followed:
Start TWRP -> advanced -> ADB sideload + swipe to activate it. Connect your phone to the computer. Open "CMD Commandline" and type "adb sideload ROMNAME.zip"
Of course "ROMNAME" has to match the zip you want to flash. Thats it
In twrp go to "REBOOT" -> "fastboot"
When fastboot usb is ready use CMD commandline again and type "fastboot flash boot boot.img"
Then you can boot android
I whished I could. As I start ADB sideload it keeps doing nothing at all until I abort it. What I think is important to know is that it is then:
"E:Unable to mout '/internal_sd'
E:Unable to mount storage.", which I think is the problem.
Flash Stock recovery And perform "factory Reset + clear storage" that will fix your storage. Then flash twrp Version 2.7 again and do what I suggested to flash the Rom
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Akkordinator said:
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Click to expand...
Click to collapse
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
You're facing sdcard bug.
This is how to solve:
1. Flash stock recovery
2. reboot to bootloader and perform "factory reset + clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again
4. Reboot recovery - mount usb storage - copy ROM.zip to sdcard // adb sideload rom
7. NOW boot android (Not at any time before! Even there is no system installed)
Please just repeat it.
LS.xD said:
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
Click to expand...
Click to collapse
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Akkordinator said:
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Click to expand...
Click to collapse
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
LS.xD said:
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
Click to expand...
Click to collapse
It was windows! Tried it on the other computer with win7 instead of 8.1 and I finally got a connection!
Thanks so much!!!
I am having MOTO G XT1032 US GLOBAL VERSION
I HAD FLASHED A DOZENS OF ROMS IN PAST USING CWM RECOVERY.....
LAST NIGHT I FORMATTED ALL THE FOLDERS USING CWM RECOVERY ......NAMELY....
/DATA
/SDCARD
/SYSTEM
/CACHE ......ETC......
I MEAN COMPLETE WIPE OUT OF THE PHONE AND FOLDERS
now MY PROBLEMS ARE.....
I DONOT HAVE ANY ROM OR ZIP IN /SDCARD TO INSTALL
I AM ABLE TO GET INTO BOOTLOADER AND RECOVERY
BUT NOT ABLE TO PUSH ANY OF THE ROMS OR ZIP FILES USING ADB FASTBOOT.
While using ADB Commands error is................ error: device not found
I Have already tried
fastboot flash recovery (of TWRP recovery over CWM recovery) i.e. I changed the recovery
adb push rom.zip /sdcard/........
adb sideload...........
but none of the above thing worked
It also shows that phone has to be rooted again and supersu is to be installed again......
I donot know how to get it working again
subodhverma21 said:
I am having MOTO G XT1032 US GLOBAL VERSION
I HAD FLASHED A DOZENS OF ROMS IN PAST USING CWM RECOVERY.....
LAST NIGHT I FORMATTED ALL THE FOLDERS USING CWM RECOVERY ......NAMELY....
/DATA
/SDCARD
/SYSTEM
/CACHE ......ETC......
I MEAN COMPLETE WIPE OUT OF THE PHONE AND FOLDERS
now MY PROBLEMS ARE.....
I DONOT HAVE ANY ROM OR ZIP IN /SDCARD TO INSTALL
I AM ABLE TO GET INTO BOOTLOADER AND RECOVERY
BUT NOT ABLE TO PUSH ANY OF THE ROMS OR ZIP FILES USING ADB FASTBOOT.
While using ADB Commands error is................ error: device not found
I Have already tried
fastboot flash recovery (of TWRP recovery over CWM recovery) i.e. I changed the recovery
adb push rom.zip /sdcard/........
adb sideload...........
but none of the above thing worked
It also shows that phone has to be rooted again and supersu is to be installed again......
I donot know how to get it working again
Click to expand...
Click to collapse
Relax no need to shout. lol. Go on fastboot and flash twrp. Then boot into recovery and select advanced rhen from there select terminal and choose any random folder. adb will now recognize your phone again so try to push the rom to /sdcard/
eg0097 said:
Relax no need to shout. lol. Go on fastboot and flash twrp. Then boot into recovery and select advanced rhen from there select terminal and choose any random folder. adb will now recognize your phone again so try to push the rom to /sdcard/
Click to expand...
Click to collapse
Thanks for a quick reply.....
I am able to get into the terminal.......... still the device is not detected.....
what command should i use on twrp terminal to pull rom and supersu in phone....
my phone battery is also getting drained off 15% remaining not charging
subodhverma21 said:
Thanks for a quick reply.....
I am able to get into the terminal.......... still the device is not detected.....
what command should i use on twrp terminal to pull rom and supersu in phone....
my phone battery is also getting drained off 15% remaining not charging
Click to expand...
Click to collapse
Super su can be automatically installed by TWRP when selecting to reboot. Okay heres my little "guide" :
http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271
eg0097 said:
Super su can be automatically installed by TWRP when selecting to reboot. Okay heres my little "guide" :
http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271
Click to expand...
Click to collapse
I went through your guide...... its was very gud
but Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
subodhverma21 said:
I went through your guide...... its was very gud
but Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
Click to expand...
Click to collapse
Check it out again i updated with pictures
eg0097 said:
Check it out again i updated with pictures
Click to expand...
Click to collapse
Thanks a lot
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot again.....
I am trying to use Flashfire v0.53 to update my Google-sourced, rooted Pixel from 7.1.0 (build NDE63X) to 7.1.1 (build NMF26V). I've downloaded sailfish-ota-nmf26v-1988a458.zip to my phone and can see it with a root file browser but when I direct Flashfire to the same directory it lists no files. Any thoughts? If I'm going about updating my phone the wrong way, I'm happy to be pointed in the right direction. Thanks.
FlashFire is not working on this phone last I heard. Flash it with TWRP.
TonikJDK said:
FlashFire is not working on this phone last I heard. Flash it with TWRP.
Click to expand...
Click to collapse
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
aholeinthewor1d said:
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187 seems promising. I can adapt to use sailfish vs. marlin. But I'm not sure how to know which image is for Verizon.
ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
fritzgerald said:
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
Click to expand...
Click to collapse
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
ChrisNelsonPE said:
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
Click to expand...
Click to collapse
That's correct. If you downloaded the OTA with System Updates then I'm not sure where it gets stored. If you downloaded it from Google then it would be in your downloads folder.
You can try the guide I wrote here to sideload the full ota zip from google.
adb sideload failure
spiller37 said:
You can try the guide I wrote here to sideload the full ota zip from google.
Click to expand...
Click to collapse
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Sounds like the driver isn't recognized. Does ADB devices list your device?
ChrisNelsonPE said:
...
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
ChrisNelsonPE said:
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
Click to expand...
Click to collapse
Alpha 2 is the wrong TWRP. You want RC1.
ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
spiller37 said:
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
Click to expand...
Click to collapse
Yes.
TonikJDK said:
Alpha 2 is the wrong TWRP. You want RC1.
Click to expand...
Click to collapse
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
I get into TWRP on my phone an do
Code:
PS C:\adb> fastboot .\twrp-3.0.2-0-RC1-fastboot-sailfish.img
< waiting for device >
on my computer and it waits forever.
ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
Power it down, hold power button and volume down to get it into fastboot.
Fastboot flash TWRPfilename.img
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
TonikJDK said:
...
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
Click to expand...
Click to collapse
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
ChrisNelsonPE said:
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
Click to expand...
Click to collapse
Unzip it into your fastboot directory. Then edit and run flashall.
So I was stupid enough to wipe all partitions (Data, system, internal storage etc) thinking that I'll do a super clean install of the new update.
Now I flash the new file (which I downloaded from the official website), it flashes just fine but gives me a bootloop.
I have (or had) root and can flash TWRP fine.
What else can I do to get back any running rom?
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Hopefully this will help you like it did with me .
Try flashiing stock boot.img from adb or try to the unbrick tool
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
railpressureflip said:
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
Click to expand...
Click to collapse
the most important thing you missed mentioning was which ROM were you ON when you wiped everything?
bcz if it was using an August security patch, and if you tried to go back to a july one without formatting data you were bound to get bootloops.
glad that it finally worked though.
but if you wanna try again, be sure to format data and your super clean install will go through.
wipe everything
format data
reboot fastboot
fastboot boot recovery
adb push stock stable ROM
flash via twrp
adb push twrp zip
flash twrp zip
reboot
now you will be fine.
speedyjay said:
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
Click to expand...
Click to collapse
Thank you very much! Sideloading rom worked for me (OP6T).