Related
Hello,
I meant to factory restore my rooted N5 and on the advanced TWRP option I chose wipe data. Now I have no OS. I'm not finding a guide on how to install the stock 4.4.2 onto my N5 using a Mac. Is there a process that shows how to do that exactly for a Mac?
thx,
Mark
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
+1 i think thts your best bet.. :good:
lesp4ul said:
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
eodchn said:
+1 i think thts your best bet.. :good:
Click to expand...
Click to collapse
Yes, I have VMWare and Windows 7 installed. But, what is the process to get the stock rom back onto my phone? I've got TWRP and able to get into Bootloader mode.
s1w999 said:
Yes, I have VMWare and Windows 7 installed. But, what is the process to get the stock rom back onto my phone? I've got TWRP and able to get into Bootloader mode.
Click to expand...
Click to collapse
Look in the general section and at the top is the guide you need to get sorted, good luck and dont panic you haven't killed it.
You don't have to do all that just sideload a stock rom onto the phone
lesp4ul said:
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol
Mac is fully supported by Android tools
Sent from my Nexus 5
Jables2915 said:
You don't have to do all that just sideload a stock rom onto the phone
Click to expand...
Click to collapse
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock or as @Pirateghost said just use the sdk to flash the image straight away.
gee2012 said:
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock.
Click to expand...
Click to collapse
100% Correct, OP can choose to do it that way or flash stock image in fastboot there's no need to use Windows at all.
Not working
Jables2915 said:
You don't have to do all that just sideload a stock rom onto the phone
Click to expand...
Click to collapse
Well, I have the Nexus Android Toolkit for oneclick root etc. I don't believe I have USB debugging "on" and I have no OS on the phone to set it to "on". The toolkit will not install the Stock rom is downloaded because is says there's a name mismatch. I choose the option to change name etc and install anyway and it just loops with the same mismatch issue.
Really frustrating. How do I download a .zip file of the rom so I can flash it. All I get are .tgz files when I download the stock rom.
Any ideas?
s1w999 said:
Well, I have the Nexus Android Toolkit for oneclick root etc. I don't believe I have USB debugging "on" and I have no OS on the phone to set it to "on". The toolkit will not install the Stock rom is downloaded because is says there's a name mismatch. I choose the option to change name etc and install anyway and it just loops with the same mismatch issue.
Really frustrating. How do I download a .zip file of the rom so I can flash it. All I get are .tgz files when I download the stock rom.
Any ideas?
Click to expand...
Click to collapse
Just put your faith in toolkits, why don`t you post your question in the toolkits thread. Let them clean up the mess Sorry if i sound a wee harsh but i HATE toolkits, they cause more problems for uneducated users than they do good.
gee2012 said:
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock or as @Pirateghost said just use the sdk to flash the image straight away.
Click to expand...
Click to collapse
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
simms22 said:
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
Click to expand...
Click to collapse
Yes i know, but OP wanted to flash back to stock and the android-sdk supports Mac computers.
gee2012 said:
Yes i know, but OP wanted to flash back to stock and the android-sdk supports Mac computers.
Click to expand...
Click to collapse
ah, i missed that :angel:
simms22 said:
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
Click to expand...
Click to collapse
I'm downloading a zip now to push/flash. It's a stock rom. Just hoping it works. Next option is I'm glad to hire someone to remote in and fix it. Let me know if you're interested.
thx
s1w999 said:
I'm downloading a zip now to push/flash. It's a stock rom. Just hoping it works. Next option is I'm glad to hire someone to remote in and fix it. Let me know if you're interested.
thx
Click to expand...
Click to collapse
Here is a tutorial for how to setup adb on Mac http://www.youtube.com/watch?v=V0MyTvgfO7s, and here is a how to use it http://forum.xda-developers.com/showthread.php?t=1917237 and restore to stock .
gee2012 said:
Here is a tutorial for how to setup adb on Mac http://www.youtube.com/watch?v=V0MyTvgfO7s, and here is a how to use it http://forum.xda-developers.com/showthread.php?t=1917237 and restore to stock .
Click to expand...
Click to collapse
Excellent, I'm headed there right now.
Thank you!
s1w999 said:
Excellent, I'm headed there right now.
Thank you!
Click to expand...
Click to collapse
OK, got that set up and ./fastboot devices shows my device serial #.
Now, as long as my USB debugging is "on" (I have no way to toggle that since I have no OS, only recovery. Does the fastboot devices command working verify that USB debugging is "on"?
Now to find instructions on how what the flash commands are.
ty
s1w999 said:
OK, got that set up and ./fastboot devices shows my device serial #.
Now, as long as my USB debugging is "on" (I have no way to toggle that since I have no OS, only recovery. Does the fastboot devices command working verify that USB debugging is "on"?
Now to find instructions on how what the flash commands are.
ty
Click to expand...
Click to collapse
Download the factory image and extract with 7-zip and find a Mac flash.all command in the fastboot folder which you can select i guess. Haven`t had a Mac ever so no xperience. Make sure you have the following img files :radio, boot, bootloader, system.img zip, cache and userdata placed in the fastboot folder.
Look here for a tutorial http://au.ibtimes.com/articles/526920/20131203/flash-factory-image-nexus-complete-stock-return.htm.
gee2012 said:
Download the factory image and extract with 7-zip and find a Mac flash.all command in the fastboot folder which you can select i guess. Haven`t had a Mac ever so no xperience. Make sure you have the following img files :radio, boot, bootloader, system.img zip, cache and userdata placed in the fastboot folder.
Look here for a tutorial http://au.ibtimes.com/articles/526920/20131203/flash-factory-image-nexus-complete-stock-return.htm.
Click to expand...
Click to collapse
Well, I've got everything in place, ./fastboot devices sees my N5 but the flash command doesn't do anything when executed.
Any ideas?
Here's what terminal shows:
Marks-Air:android tools Mark$ ./fastboot devices
0591a238002ead35 fastboot
Marks-Air:android tools Mark$ ./flash-all.sh
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
Marks-Air:android tools Mark$
I have searched and can't find out anything about this, but for some reason I can flash recovery-clockwork-6.0.4.5-hammerhead.img through fastboot and then get into CM recovery. However, if I leave recovery and try to boot into it again, I get the dead droid picture. I can flash CM again and it'll work, but again, for a single use. I've never had this problem before on any Droid I've owned and I can't seem to find anyone dealing with it in this forum. Any help would be greatly appreciated.
No this phone is not rooted. I have unsuccessfully attempted this with CM (upon exiting recovery mode, you are prompted to root your phone if it hasn't been rooted).
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
You should also search the rules and list in he correct forum. This is not for questions only development
Sent from my Nexus 5 using XDA Free mobile app
also, clockwork mod recovery is long discontinued and provides no support anymore.
EddyOS said:
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
Click to expand...
Click to collapse
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
strakajagr said:
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
Click to expand...
Click to collapse
In any case, I can flash something else since CM is no longer supported. Thanks.
strakajagr said:
In any case, I can flash something else since CM is no longer supported. Thanks.
Click to expand...
Click to collapse
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How do I go about locking the bootloader after it's unlocked?
strakajagr said:
How do I go about locking the bootloader after it's unlocked?
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
BirchBarlow said:
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
Click to expand...
Click to collapse
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
strakajagr said:
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
Click to expand...
Click to collapse
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
simms22 said:
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
Click to expand...
Click to collapse
Word. Thanks.
Next order of business is figuring why there is so much lag when I text/gchat in 5.0. This is the whole reason I got into this mess. I couldn't wait 3 more weeks. Sadly, when I type, the keyboard freezes constantly. I figure I'll install a recovery mode correctly and then try to tackle that problem.
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Use bluespark or black themed twrp
https://forum.xda-developers.com/showpost.php?p=77748695&postcount=7
another member is having the same issue, here's my recommendation. let me know if it helps please.
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Same situation, same problem. I tried:
Code:
fastboot boot twrp-3.2.3-x_blu_spark_v9.85_op6.img
and still I end up in CrashDump Mode.
mackler said:
Same situation, same problem. I tried:
and still I end up in CrashDump Mode.
Click to expand...
Click to collapse
Use v9.86
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Works. Thank you!! :victory:
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Same, that was the issue, thanks!
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Giodude12 said:
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Click to expand...
Click to collapse
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
MrSteelX said:
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
Click to expand...
Click to collapse
Just looked into it. For whatever reason it doesn't work on Android p unless I run the uninstaller first. Thanks for the help though, I'm all good.
Use v9.86 of ... ??
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Use v9.86 of what ??
dash_z1 said:
Use v9.86 of what ??
Click to expand...
Click to collapse
Blu spark twrp..
Thank you
whizeguy said:
Blu spark twrp..
Click to expand...
Click to collapse
thank you just reialized that i`m supposed to use blue spark version of twrp for my op6 although they provided the original twrp links which was misleading in the root post
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Bubba Fett said:
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Click to expand...
Click to collapse
What fastboot commands have you tried?
mikex8593 said:
What fastboot commands have you tried?
Click to expand...
Click to collapse
Fastboot devices
Fastboot boot twrp. Img
It used to work. It shows through adb that it was successful but op6 reboots to fastboot mode in the center of the screen. I can get the phone recognized by adb when the screen has a green start sign on top.
Bubba Fett said:
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Click to expand...
Click to collapse
Unbrick tool
Bubba Fett said:
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Click to expand...
Click to collapse
use this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
siddhrsh said:
use this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
I have that downloaded and ready as my last resort. I was trying to avoid wiping the whole device again but if that's what I have to do I will. Thanks.
Bubba Fett said:
I have that downloaded and ready as my last resort. I was trying to avoid wiping the whole device again but if that's what I have to do I will. Thanks.
Click to expand...
Click to collapse
Remove -w from command
siddhrsh said:
Remove -w from command
Click to expand...
Click to collapse
Ooohh yeah! Thanks man! Have a good New Years!
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
zioloiso said:
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
Click to expand...
Click to collapse
Yes, this here is that stock recovery WITH ADB ENABLED.
iruiz2 said:
Yes, this here is that stock recovery WITH ADB ENABLED.
Click to expand...
Click to collapse
default recovery is without ADB Enabled?
zioloiso said:
default recovery is without ADB Enabled?
Click to expand...
Click to collapse
no stock recovery does not come with module enabled...you can try it yourself just boot to recovery and try adb shell
thats why i did it.
parag60288 said:
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
believe it should its just a recovery, i believe the ROM localization is where the real difference is...the stock recovery eitherway comes in some chinese and english...no indian language.. and in the end you can still reflash stock if you need to do anything there with it. Eventhou i am flashing only through bootloader...never really used it except adb shell
killswitx said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
Click to expand...
Click to collapse
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
bynarie said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
reboot into recovery u can use as well:
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
In theory, we should be able to make a backup of our own boot.img with this?
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
I just DD'd boot.img. This seemed to work for backing up partitions.
Recovery images don't differ across variant models do they?
This would work on global version for instance?
shorty1993 said:
Recovery images don't differ across variant models do they?
This would work on global version for instance?
Click to expand...
Click to collapse
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
grandpajiver said:
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
Click to expand...
Click to collapse
Please do. Would rather use the global if possible.
shorty1993 said:
Please do. Would rather use the global if possible.
Click to expand...
Click to collapse
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
grandpajiver said:
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
Click to expand...
Click to collapse
Are there differences between the Global and EU recoveries?
iruiz2 said:
Are there differences between the Global and EU recoveries?
Click to expand...
Click to collapse
wouldn't say there ist much difference.. its just recovery
Sent from my [device_name] using XDA-Developers Legacy app
obol2 said:
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
Click to expand...
Click to collapse
Can you please explain me how you did it ?
samyhaff said:
Can you please explain me how you did it ?
Click to expand...
Click to collapse
Boot into recovery, go in cmd and type adb.
type
dd if=/dev/block/bootdevice/by-name/boot_a of =/data/media/0/nameoffile.img
dd if=/dev/block/bootdevice/by-name/boot_b of =/data/media/0/nameoffile.img
patch one of them in magisk manager, fastboot boot patched img, direct install magisk in magisk manager