Develop Bugs

[Q] iOS System Wipe

Hey XDA Members
I know there has already been similar posts to mine on XDA as I've worn out the search button on google trying to find a solution to my problem, with no avail. So I thought I would leave a description of my own situation and see if a more tech-savvy individual could kindly help me out...
So yesterday I decided it would be a good idea to unlock my bootloader & root my device simply because I wanted to remove all the bloatware which HTC 'generously' crammed into the One X. Unlocking the bootloader was simple enough following the instructions provided. However, rooting my handset was not so effortless. The root was ineffective & I got stuck with yet another unwanted app called SuperSU! (An error message regarding missing binary codes appeared every time I tried to open the application) I tried uninstalling via both settings & google play before finally factory resetting my phone. None of these methods worked
At this point it suddenly dawned on me someone so unenlightened in the art of software development or anything android related shouldn't being toying with stuff he can't afford to break! But I figured it was too late to turn back now and continued in my moment of intellectual darkness...
In my bewildered state I accidentally 'wiped system' using CWM and now I have no iOS. My HTC will only boot until the 'quietly brilliant' slogan appear's & no further. When I connect my phone to my computer via USB I can not access the removable storage device, a removable disk appears but when clicked I am prompted to 'insert removable disk'. I am lead to believe from reading related threads that if I had access to my phones storage then installing a new iOS would be relatively straight forward. Also trying to mount in CWM just retrieves an error message reading 'CWM unable to open ums lunfile (no such directory exists)'. Where do I go from here?
Any help would be much appreciated :fingers-crossed:

Flash a newer recovery, try the latest Philz touch recovery then you should be able to mount sdcard and flash a rom

Hope it helps
if tthe above suggestion doesnt work, try this
http://www.hackmyandroid.com/comprehensive-guide-on-unbricking-the-htc-one-x/4216
I recommend you flash the latest TWRP recovery since it gives you access to the phones sdcard, if your staying stock/near stock OS you can check http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html download the Download stock odexed 4.18.401.3, and just flash it in recovery or you can download w.e custom OS you like and flash it the same
Hope it helps

Thank you both for your replies :good:
m.jordan, I tried to flash TWRP onto my device (3 different versions in fact) but once entering recovery mode I was prompted to 'swipe screen to unlock' which wasn't possible because I can only use the volume controls and the power button. After that I downloaded the latest version of CWM which enables me to both use the control buttons & touch screen. I downloaded the 'stock odexed 4.18.401.3' although I have no way of flashing on my device...
I tried the method in the link you kindly provided and followed each instruction carefully. After re-unlocking my bootloader (does it matter whether the device is locked or unlocked when mounting USB storage in recovery mode?) & flashing CWM I downloaded the odexed 4.18.401.3 extracted boot.img & flashed that too. On the website you shared it then prompted me to 'mount usb storage' & my device should now be showing as 'clockworkmod' so I would be able to place the odexed 4.18.401.3.zip into the folder and then flash my handset. Unfortunately I still have no removable disks showing on my PC
My HTC One X does not have removable storage (I suppose you already knew that) & I havn't been able to get my PC to read a removable disk since the day I wiped the system.
If only I could get my computer to show an 'adb device' I'm sure this would be so much easier! I don't suppose you would know anything about that? when I use cmd prompt 'adb device' most of the time it just returns:
adb out of date. killing...
daemon started sucessfully
list of attached devices
Nothing ever shows under attached devices
Nogotaclue, my next step it to try Philz recovery & see where that takes me, i'll let you know how that goes (Although I fear it will just have the same outcome as the rest & not be able to read an sdcard)
Thanks again

well it seems if you could follow the steps on that link, then your pc is recognizing the device so there is hope. If TWRP isnt working then cool. On either the CWM or Philz there is an option called adb sideload rom, if you can't access your SD card you can always sideload and install the rom using either One_X_All-In-One_Kit or WinDroid Universal HTC Toolkit v1.1, made them available here https://www.dropbox.com/sh/fv9fun4x2c4dk2l/AABhNHvlpPUvDXUWYK5PJNhpa?dl=0
Once in recovery I believe its under the install option, you have the option to install rom from sdcard and sideload rom, just select sideload. once thats done, open either the all in one or windroid with your device connected to your pc (i recommend the all in one), select the option to sideload, and cross your fingers that it works

ProdiJay said:
Thank you both for your replies :good:
m.jordan, I tried to flash TWRP onto my device (3 different versions in fact) but once entering recovery mode I was prompted to 'swipe screen to unlock' which wasn't possible because I can only use the volume controls and the power button. After that I downloaded the latest version of CWM which enables me to both use the control buttons & touch screen. I downloaded the 'stock odexed 4.18.401.3' although I have no way of flashing on my device...
I tried the method in the link you kindly provided and followed each instruction carefully. After re-unlocking my bootloader (does it matter whether the device is locked or unlocked when mounting USB storage in recovery mode?) & flashing CWM I downloaded the odexed 4.18.401.3 extracted boot.img & flashed that too. On the website you shared it then prompted me to 'mount usb storage' & my device should now be showing as 'clockworkmod' so I would be able to place the odexed 4.18.401.3.zip into the folder and then flash my handset. Unfortunately I still have no removable disks showing on my PC
My HTC One X does not have removable storage (I suppose you already knew that) & I havn't been able to get my PC to read a removable disk since the day I wiped the system.
If only I could get my computer to show an 'adb device' I'm sure this would be so much easier! I don't suppose you would know anything about that? when I use cmd prompt 'adb device' most of the time it just returns:
adb out of date. killing...
daemon started sucessfully
list of attached devices
Nothing ever shows under attached devices
Nogotaclue, my next step it to try Philz recovery & see where that takes me, i'll let you know how that goes (Although I fear it will just have the same outcome as the rest & not be able to read an sdcard)
Thanks again
Click to expand...
Click to collapse
Man flash Philz 5.15.9 mount your sd card and you are ready to go only in this version sd card mount work no TWRP no CWM exactly Philz 5.15.9

[Q] Wifi Model, Stuck on Google Boot Up Screen, No OS Installed says TWRP, help?

Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.

kevs888 said:
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
Click to expand...
Click to collapse
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)

graphdarnell said:
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
Click to expand...
Click to collapse
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!

kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.

kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
Fastboot page

graphdarnell said:
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
Click to expand...
Click to collapse
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2

kevs888 said:
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
Click to expand...
Click to collapse
If you're comfortable using the ToolKit, you don't need an OTG cable. Connect your tab to PC, fire up ToolKit, complete all the prelim BS, then flash the bootloader from TK. Do not use TWRP for this. To do this, open the ToolKit folder in drive C:, locate the folder therein for zips, place the zip files (4.05 bootloader; TWRP; or custom roms) in there, and start to install. I am talking off the top of my head. But give me a few minutes to check the Kit again, and I'll give specific instructions. Bear with me, as I'm on Linux at the moment and therefore cannot start ToolKit (which is in Windows).

Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.

graphdarnell said:
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
Click to expand...
Click to collapse
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!

kevs888 said:
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
Click to expand...
Click to collapse
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.

graphdarnell said:
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
Click to expand...
Click to collapse
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.

kevs888 said:
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
Click to expand...
Click to collapse
I'm glad you got it working again. Sorry you had to make a trip to the store. You should've waited for KT to switch the tab to TWRP 2711 for you. But it was not a waste of time anyway.

Oneplus 3 do not boot after installing OxygenOS 4.0.2

Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin

Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.

dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.

Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.

I think I bricked my ZE551ML_Z00A

Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.

Yuno17 said:
Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Click to expand...
Click to collapse
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?

Yuno17 said:
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Click to expand...
Click to collapse
very first of all uninstall everything especially i soc drivers and xFSTK. then disable driver signature enforcement. and go to thread above posted and do step by step.
how to disable signature enforcement and install driver on win 10 see in thread above

device keeps rebooting to twrp

Guys,
My father got my op5t with root, I think he had oreo oxygen os rom, after a couple months, he entered twrp by accident and he whiped, he did not know what he was doing. Long story short, the device keeps rebooting to twrp bluespark 3.2.1 v8.78. When the device is in twrp, i tried to connect to the pc but it wont detect the device.
My question; how can I fix this, I downloaded (OnePlus5TOxygen_43_OTA_034_all_1804201221_5c1b6d44ac9) but I dont know how to put in the device in order to install the zip file through twrp to restore Oxygen Os.

Hold the power+volume down buttons together and don't let go until you reach the twrp load up menu.
Stick the zip file into a storage format that hooks up to the USB-C, go into twrp and switch from internal storage to USB OTG and flash it from there.
I'm not too sure about this next method but you may be able to hook your phone up to the computer and have it on TWRP, you might have to look for the setting in the menus, then find the phone from your PC and drag the file onto the phone. I assume you know the steps in how to flash a new ROM.
Just a reminder, you'll have to be on , 5.1.7 Oreo to make the jump to 9.0 pie oxygen OS. Do you know what version he was on? You might have to just go into download mode and use ADB to flash the file.

kaslopis said:
Hold the power+volume down buttons together and don't let go until you reach the twrp load up menu.
Stick the zip file into a storage format that hooks up to the USB-C, go into twrp and switch from internal storage to USB OTG and flash it from there.
I'm not too sure about this next method but you may be able to hook your phone up to the computer and have it on TWRP, you might have to look for the setting in the menus, then find the phone from your PC and drag the file onto the phone. I assume you know the steps in how to flash a new ROM.
Just a reminder, you'll have to be on , 5.1.7 Oreo to make the jump to 9.0 pie oxygen OS. Do you know what version he was on? You might have to just go into download mode and use ADB to flash the file.
Click to expand...
Click to collapse
thnx for response, but I said from the start that I believe that he was running oreo, im sure he was not on pie, it could be oreo or nougat but I think oreo. USB otg does not work for me, otherwise I would have tried that, I dont have the equipment.
The other method you mentioned about adb, If I go to twrp, click on advaned then you can click adb sideload, from there you should swipe to start sideload I believe, then open cmd in winodws and type ''adb sideload'' then drag the zip file to cmd and hit enter, however it says; cannot read 'E:\op5t restore stock\OnePlus5TOxygen_43_OTA_034_all_1804201221_5c1b6d44ac9.zip
How should I proceed ?

hold on, I found an option to enable mtp in twrp, now the pc finds the device, let me put the stock rom 5..1.1 that I downloaded and report back how it goes.

after flashing te the stock zip file, the devicr was in bootloop, then I figured I had to uninstal Magisk with the magisk uninstal zip file, after that the device booted fine.
thnx for the help anyways, really appreciated it ^^