Related
I recently sold my Wildfire S, and because of that I wanted to wipe the phone out. So, I went to install a ROM, the same m1 mix I have been using for months, and I tried to install it again.
> Stays at HTC white screen and will forever if I let it.
> Tried installing another ROM to see if it was just corrupt. No go.
> I can get to the HBoot screen and move around but I can't get past HTC screen after installation is complete!!!
> Tried installing CWM again to see if it was an issue there, but now I get a "Install Fail" message because the ID is incorrect (I assume it has to do with the golf card)
I just want the damn thing to boot and work, I don't even care if it goes back to stock, I just need it to work. What are my options here? Any help would be great. An important factor I should mention is that I am on a Mac, and only have access to a Mac.
Thanks!
I have an evo so I'm not sure how things work on your phone but have you tried an ruu? It should help
Sent from my PC36100 using xda premium
Are you wiping data/factory reset, cache and dalvik? You need to do this in cwm
Yes, I always wipe both system and cache, as well as dalvik.
I will try a RUU, see where that gets me. Thanks. And if anyone else has suggestions please let me know!
I think you can only run an ruu under windows.
I could be wrong though.
I can't just have the ZIP on my SD Card and install it from there?
You can but I think it will give you the same issue.
Try it though, its worth a shot
I just want the easiest way to get this back to functioning. I don't need any of the data on the phone or the SD card. I just wanted it to work. Period.
Easiest and safest is ruu
Do you not know anyone that will let you run it on their windows machine?
It would take 10 mins topps and is almost guaranteed to get you back up and running.
By the way are you a GSM or cdma user?
Edit: is that rom overclocked by default? The reason I ask is a lot of people have been having issues like you when installing Rom's that are pre overclocked.
Check if there's a default clock speed kernel on his op
GSM Virgin Mobile Canada.
nootered said:
GSM Virgin Mobile Canada.
Click to expand...
Click to collapse
Also your bootloader must be locked in order for the ruu to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am unlocked currently. I have been running it just fine with the m1xd ROM, all the stats are in my sig.
I just want this facking thing to function!!!!!!!!!!!! :O
nootered said:
I recently sold my Wildfire S, and because of that I wanted to wipe the phone out. So, I went to install a ROM, the same m1 mix I have been using for months, and I tried to install it again.
> Stays at HTC white screen and will forever if I let it.
> Tried installing another ROM to see if it was just corrupt. No go.
> I can get to the HBoot screen and move around but I can't get past HTC screen after installation is complete!!!
> Tried installing CWM again to see if it was an issue there, but now I get a "Install Fail" message because the ID is incorrect (I assume it has to do with the golf card)
I just want the damn thing to boot and work, I don't even care if it goes back to stock, I just need it to work. What are my options here? Any help would be great. An important factor I should mention is that I am on a Mac, and only have access to a Mac.
Thanks!
Click to expand...
Click to collapse
Hello ,
this will return your phone to stock state (means that you will no longer have CWM recovery and you will have to install it again after this. If unlocked with XTC Clip YOU WILL STAY S-OFF ,I didn`t tried it with device unlocked via HTC Dev)
STEP BY STEP instructions what you should do :
1. go to http://forum.xda-developers.com/showthread.php?t=1432474
2. download http://www.mediafire.com/?ksa9k8dmxexdkdo
3. follow the instructions from 1
4. click thanks button
credits to Gig11gs & Ping192
P.S. I`m not responsible if you do any damage to your device.
if you have a backup or something then flash it through hboot
or if you have a extracted zip file from an ruu (rom.zip file in c:/temp when you run the installer) then extract it to desktop and flash it through hboot(if the file name of system is system.yaffs2.img then change it to system.img , you require only two files boot.img and system.img so no need to extract everything just extract these two)
the codes for both are
(locate the adb files first.)
in my case i have copied fastboot file from tools folder of sdk on desktop and also adb and adbbin.dll on desktop.. if you also copy these files on desktop then run the following exact commands when you are on bootloader the fastboot option will be highligted press power buton to select it .. when you in fastboot menu connect phone to pc and then write these command in dos prompt (go to start menu , run then write cmd and press enter you will have a dos prompt open)
Code:
cd desktop
fastboot flash boot boot.img
fastboot flash system system.img
when done go to recovery and now do all format data , clear chache and dalvik chace your phone will be un rooted total stock
It worked for me.. credits to EOgan
Or you can go to this tutorial that will downgrade everything even hboot and radio at http://forum.xda-developers.com/showthread.php?t=1540952 and remember o thank me
Just a thought but have you wiped everything before flashing the ROM? I've had a weird experience once with pretty much the same issue (stuck on splash screen). Wiping everything (system, data, cache, boot AND SD Card) seemed to have resolved the issue. If you're using an already partitioned card, I'd recommend powering off after CWM flashing, unmounting the SD and then turning it on.
This should work actually (don't see a reason not to). Also, if you've modified the ROM.zip file in any way after downloading it, I'd advise flashing one which is freshly downloaded rather (would eliminate any user tweaks causing the issue).
PS. I've attached a flashable superwipe script which you can run before flashing the ROM. Let me know how it worked out for you.
I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong
Thanks for pointing that out! It's actually a 16GB 550.
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.
ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.
ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...
Right, correct. I can get into recovery, and fastboot works, but not ADB.
ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.
Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.
Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.
Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.
i have similar problem too
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
https://imgur.com/a/w4DWq
If the attached images do not load, then I have uploaded the images on Imgur
did you unlock the critical partition as well? Maybe that's the problem?
anthony.moua95 said:
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
Click to expand...
Click to collapse
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Badger50 said:
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Click to expand...
Click to collapse
I am on 8.1 and updated it via OTA.
anthony.moua95 said:
I am on 8.1 and updated it via OTA.
Click to expand...
Click to collapse
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Have you tried a different cable yet?
Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Oh geeze, this is something I can't be bothered with at the moment with my current situation (living and working in Thailand). I appreciate all the input that you have given on this thread though! I think I will just keep my phone where it is at now then (unlocked bootloader, 0 modifications, 8.1.0). But I will continue to follow and see if there are any definitive or streamlined solutions to this potential problem in the (near) future. Adaway and Viper4Android are still very important enough reasons for me to root.
I will also add that when I tried rooting via the magisk method (patch_boot.img), I kept getting a message along the lines of
"target didn't report max-download-size
sending 'boot' (x KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.123s"
Although even though despite always getting a message like this, I was able to somehow get root successfully one time. I decided to unroot and try to duplicate the root result but to no avail. Also got that annoying "internal problem with your device" message and followed @topjohnwu's tutorial only to get the "target didn't report max-download-size...FAILED (remote: Requested download dize is more than max allowed)" message again.
My laptop is currently running Manjaro (based on Arch Linux) but I can't imagine it being the reason I keep getting that "target didin't report max-download-size" message.
ilal2ielli said:
Have you tried a different cable yet?
Click to expand...
Click to collapse
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
equlizer said:
did you unlock the critical partition as well? Maybe that's the problem?
Click to expand...
Click to collapse
I've tried numerous times and it always gave me a fail message or acknowledgement that my phone was already unlocked I'm giving up until I see a more streamlined answer to this potential problem
Make sure you adb/fastboot is up to date, it has caused many headaches for people trying to use older versions.
Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
anthony.moua95 said:
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
Click to expand...
Click to collapse
I'd say try to get another cable ASAP, especially if anything else you do doesn't work.
When I first was attempting to unlock my bootloader, nothing worked when I was using third-party cables.
Luckily, my laptop had a USB-C port, so I was able to use the stock USB-C cable and I haven't had any problems since.
trim81 said:
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
Click to expand...
Click to collapse
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Badger50 said:
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Click to expand...
Click to collapse
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
trim81 said:
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
Click to expand...
Click to collapse
Ok cool, that's the only way I know how to do it as well. Cool beans, thanks bro :good:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
cavolo said:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
Click to expand...
Click to collapse
Dude, if that's the answer, which it probably is, I'm gonna pull my hair out. Been trying everything I can to these folks out. And it's a flippin 8 dollar cable! Oh well, live and learn
I know tou probably did this already but I did not see it posted.
You did enable developer settings and enable oem unlock in developer settings?
Is there a solution to this issue? I have followed every set of directions I can find on XDA and beyond, wiped and wiped, locked and unlocked my phone a few different times. Tried different cables and different ports on my computer. No matter what I do, I am stuck at the "downloading boot" after trying to flash TWRP. Thanks in advance for any help.
Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....
Everything about this issues is already said in this forum.
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.
Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Reserved !!
hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp
iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588
raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome
Why it wait forever for attached device, even removing and reconnecting phone?
Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.
I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue
PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.
(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)
Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first