Related
Hej guys. I really hope that you can help me with my problem
Have been trying for 2 days and looking at post but haven't been able to get it fixed.
Here goes.
I have been playing around with custom roms on my htc one for a while now.
Then when i was about to install a new custom rom, i first wiped my phone.
I properly wiped something that should not be wiped, because i ended up with no os and no custom rom zip file that i could install in twrp.
I then tryed sideloading revolutions, and it seemed to work because it ended up booting on the phone and i could select what programs too install with it... but halfway through it stoped and rebooted.
now i cant even get into recovery anymore, and booting the phone only gets it to htc briliant logo. Then it restarts and tryes going into recovery, but it cant, and ends up just restarting over and over again.
Tryed flashing cwm and twrp again, but still cant get into recovery.
adb dont fint my device, and i have tryed all drivers i could find.
Tryed using a RUU, but it fails. Properly because its not the right one, but cant fint one that fits.
Sooo... i think im in a real pickle right now.
my radio is :4a.14.3250.13
hboot: 1.44.0000
Thinking about going back with my phone, but with the warranty gone i dont know if they'll even look at it.
Hoping for some advise, or some ideas on what to do.
-dealba
fastboot erase cache in terminal or with all in one toolkit
Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?
dealba said:
Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?
Click to expand...
Click to collapse
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm
skinsfanbdh said:
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm
Click to expand...
Click to collapse
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/
dealba said:
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/
Click to expand...
Click to collapse
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish
skinsfanbdh said:
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish
Click to expand...
Click to collapse
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
you on a windows computer?
dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)
skinsfanbdh said:
you on a windows computer?
Click to expand...
Click to collapse
Yes, im running windows
dealba said:
Yes, im running windows
Click to expand...
Click to collapse
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands
rambo12345 said:
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)
Click to expand...
Click to collapse
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..
dealba said:
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..
Click to expand...
Click to collapse
adb sideload
its an option in the all in one tool kit but its easier or you can type the command
skinsfanbdh said:
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands
Click to expand...
Click to collapse
I got the toolkit now
got a 5 min post restriction so little slow on replying
dealba said:
I got the toolkit now
got a 5 min post restriction so little slow on replying
Click to expand...
Click to collapse
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions
skinsfanbdh said:
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions
Click to expand...
Click to collapse
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it
dealba said:
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it
Click to expand...
Click to collapse
no problem. have fun:victory:
skinsfanbdh said:
fastboot erase cache in terminal or with all in one toolkit
Click to expand...
Click to collapse
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******
How do you copy update.zip from external to internal SD?
Sorry if it's a total no-brainer, but how do I manually copy a recovery zip to the internal update.zip? Can I do this from my phone (which is stuck in a bootloop: see below)? Or do I have to use ADB with my computer?
Turbojugend said:
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******
Click to expand...
Click to collapse
My situation:
Using Open Recovery I tried to install CM7 with custom kernel on my XT720
It gave an error: "assert failed: write_raw_image... Status 7" As I was looking that up, my phone blackscreened. After a while I pulled the battery.
Then on startup it went into a bootloop after a picture of a broken screen saying "2ndboot kernel restart in progress." (Presumably the kernel wasn't properly applied?)
Trying to boot into bootloader says battery is too low.
Phone will only turn on when plugged into outlet.
What I think I need to do:
- Copy a good update from my external SD over the bad update.zip on the internal SD, and apply the update to reset the kernel, etc.
- Open Recovery could do this, if I could load it.
- I could load Openrecovery if I could get the bootloader to run,
- I could get the bootloader to run if my battery would charge
When in TWRP 2.5.0 if I have a Sprint HTC One, and want to flash other ROMs after flashing a 4.2.2 will my recovery still recognize the usb/otg and be able to flash those ROMs stored on there?
dantonuci said:
When in TWRP 2.5.0 if I have a Sprint HTC One, and want to flash other ROMs after flashing a 4.2.2 will my recovery still recognize the usb/otg and be able to flash those ROMs stored on there?
Click to expand...
Click to collapse
I thinks the OTG/USB function is depended on Recovery itself.
What system you've flashed is not the point.
kivx said:
I thinks the OTG/USB function is depended on Recovery itself.
What system you've flashed is not the point.
Click to expand...
Click to collapse
I can confirm.
It depends from recovery and not from rom.
However, you can use adb push or sideload and not the OTG...
Guich said:
I can confirm.
It depends from recovery and not from rom.
However, you can use adb push or sideload and not the OTG...
Click to expand...
Click to collapse
perhaps I mispoke, I know that the Recovery doesn't recognize the sd card files on the twrp after a 4.2.2 flash but I figured an external source shouldn't be affected by the partition adjustment relative to 4.2.2 and I was curious if one could not access internal storage if they could still flash a rom from a zip drive connected to adapter aka usb/otg option , Guich are you telling me no, but you can adb push or sideload excuse me if I sound redundant as I am basically quoting the last bit of your post, just want a definitive answer that the otg/usb option is not available to flash roms with if you have gone from 4.1.2 to a 4.2.2 rom or do you have to do the adb push or sideload method. I am currently not in this position but have was considering flashing some of the great 4.2.2 roms out there and wanted to not have to sideload or adb push as I am a mac owner until I get an old desktop/pc to program with.
dantonuci said:
perhaps I mispoke, I know that the Recovery doesn't recognize the sd card files on the twrp after a 4.2.2 flash but I figured an external source shouldn't be affected by the partition adjustment relative to 4.2.2 and I was curious if one could not access internal storage if they could still flash a rom from a zip drive connected to adapter aka usb/otg option , Guich are you telling me no, but you can adb push or sideload excuse me if I sound redundant as I am basically quoting the last bit of your post, just want a definitive answer that the otg/usb option is not available to flash roms with if you have gone from 4.1.2 to a 4.2.2 rom or do you have to do the adb push or sideload method. I am currently not in this position but have was considering flashing some of the great 4.2.2 roms out there and wanted to not have to sideload or adb push as I am a mac owner until I get an old desktop/pc to program with.
Click to expand...
Click to collapse
What I meant was that as long as the recovery you're using supported OTG/USB method, you can install any ROM you want.
4.1.2 or 4.2.2 doesn't matter.
kivx said:
What I meant was that as long as the recovery you're using supported OTG/USB method, you can install any ROM you want.
4.1.2 or 4.2.2 doesn't matter.
Click to expand...
Click to collapse
cool so even if the sd card is unreadable it will still be able to read and flash roms from usb/otg option, GREAT! Thank you folks !
I can't seem to find a solution to the problem I am having and I spent 5 hours looking at many threads over many forums.
I was trying to restore my stock GPE in order to send to repair, but I accidentally wiped of everything and ended up with no OS installed. I tried then using fastboot/adb to install through recovery, (TWRP) I am able to use fastboot however adb will not see my device therefore I am not able to push any .zip to install GPE Android 4.3
Tried flashing stock.zip, but get the error "remote 12: signature verify fail", then I noticed that it is "S-On"
I am hopeless right now, but I know there is something that can be done or I am missing/screwing something.
Is there any other way in which I can restore my HTC One to GPE Android as initially shipped? I just need to fix this because I have a repair order going.
Any help will be highly appreciated.
In recovery you can see your sd card?
adb drivers are ok?
When the phone is in recovery the pc can detect it?
Guich said:
In recovery you can see your sd card?
adb drivers are ok?
When the phone is in recovery the pc can detect it?
Click to expand...
Click to collapse
In recovery I do see /sdcard, however HTC One does not have sd card.
I tried downloading some drivers, maybe not the most up to date ones, do you have a link where I can download these?
I did not see if the PC could detect it while in recovery, I will check that and let you know.
vaguitovera said:
In recovery I do see /sdcard, however HTC One does not have sd card.
I tried downloading some drivers, maybe not the most up to date ones, do you have a link where I can download these?
I did not see if the PC could detect it while in recovery, I will check that and let you know.
Click to expand...
Click to collapse
Try to use this adb drivers.
However, let me know if, in device manager, you can see your one.
I have noted that CWM shows ADB drivers quickly than TWRP... perhaps try flashing CWM, adb push your_rom.zip /sdcard, and then flash TWRP if necessary, or just install using CWM..
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.
Ok, cheers. I'll get a usb otg cable and give it a go.
HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.
purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!
First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.
purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.
It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!
Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.
ad
Ducky10100 said:
Hello guys. I've got a big problem. I rooted my Nexus 6 and installed TeamWin Recovery, but something wasn't installed correctly so I went to factory reset my phone from TeamWin recovery and completely deleted EVERYTHING, including my OS. Now I cannot do anything, my phone just stays at the Google logo. Just to clear things up:
My phone isn't rooted
Bootloader isn't unlocked
I have no OS.
I need help on how to flash android 5.0 back on my Nexus (Yes I've tried using Toolkit, but since my phone doesn't boot it's no use to me). Help would be much appreciated.
Click to expand...
Click to collapse
I dont mean to sound rude, really, but so what? you can download and transfer a ROM to your twrp recovery via regular file transfer, adb sideload, or adb push. so download what you need, choose a method, then transfer it to your phone. you dont have other options, besides for flashing a factory image.
Why did you install a custom recovery if you haven't unlocked your phone?
It seems to me you should start by downloading the appropriate factory image from Google. And flash everything (with the exception of boot loader) from inside your boot loader. Press and hold the power button while it's on, this will set a reboot. While the screen is black, press and hold power and volume down. This will get into boot loader.
Let us know if you need assistance on how to flash the factory images.
brymaster5000 said:
Why did you install a custom recovery if you haven't unlocked your phone?
It seems to me you should start by downloading the appropriate factory image from Google. And flash everything (with the exception of boot loader) from inside your boot loader. Press and hold the power button while it's on, this will set a reboot. While the screen is black, press and hold power and volume down. This will get into boot loader.
Let us know if you need assistance on how to flash the factory images.
Click to expand...
Click to collapse
I had my phone rooted and unlocked, but I reset everything and that's when it happened.
simms22 said:
I dont mean to sound rude, really, but so what? you can download and transfer a ROM to your twrp recovery via regular file transfer, adb sideload, or adb push. so download what you need, choose a method, then transfer it to your phone. you dont have other options, besides for flashing a factory image.
Click to expand...
Click to collapse
Hey dude if you can point me to where I can download one and a tutorial I will, but I've tried almost everything and nothing seems to work.
Ducky10100 said:
Hey dude if you can point me to where I can download one and a tutorial I will, but I've tried almost everything and nothing seems to work.
Click to expand...
Click to collapse
first off, look at your recovery, you should be able to find a mtp and a adb sideload option. mtp would be the regular file transfer. you can google adb sideload twrp, and youll find instructions on that. or you can try googling adb push, and you will find instructions. thats the one i normally would use(but its been a long time), ive deleted my os before as well :angel:
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
here's something I just found about adb sideload http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
simms22 said:
first off, look at your recovery, you should be able to find a mtp and a adb sideload option. mtp would be the regular file transfer. you can google adb sideload twrp, and youll find instructions on that. or you can try googling adb push, and you will find instructions. thats the one i normally would use(but its been a long time), ive deleted my os before as well :angel:
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Click to expand...
Click to collapse
Okay thanks man.
reflashing stock via wugs nexus tool as bricked should help.
(this helped me, just read it didnt help you, did you try as bricked/softbricked? (sorry not sure what it is))
rhystagram said:
reflashing stock via wugs nexus tool as bricked should help.
(this helped me, just read it didnt help you, did you try as bricked/softbricked? (sorry not sure what it is))
Click to expand...
Click to collapse
Overkill. You can just put a ROM zip on the sdcard and flash it via TWRP recovery
danarama said:
Overkill. You can just put a ROM zip on the sdcard and flash it via TWRP recovery
Click to expand...
Click to collapse
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
rhystagram said:
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
Click to expand...
Click to collapse
Internal storage is called sdcard. All you need to do is boot TWRP and connect to PC. You should see your internal storage on your PC then. Drag and drop your ROM from PC to internal storage. Flash ROM, profit.
rhystagram said:
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
Click to expand...
Click to collapse
/sdcard is a common directory mounted at /data/media/0. TWRP has MTP access so like android, you plug it into the computer and drag files across. You don't need to remove it to do that.
...and indeed you are right, if you delete the "internal storage"/as s it shows up as in MTP mode, you would have to flash stock (though we'd recommend using fastboot not toolkits) however that is not the case here. The user said he deleted " everything" via TWRP. Although there is an option to "wipe" internal storage, this only wipes the /sdcard data - NOT deletes "internal storage" as someone can do on a computer. So yeah, the quickest and best way to recover from "deleted OS" is to put a ROM.zip on the sdcard and flash it.
Will someone please refer me to a download for Android 5.0. I've tried some, but all the sites are block by my internet provider.
Ducky10100 said:
Will someone please refer me to a download for Android 5.0. I've tried some, but all the sites are block by my internet provider.
Click to expand...
Click to collapse
There is only one legitimate site for Google factory images, and it's linked below. I don't understand why any provider would block it...
And why do you want 5.0? That is the original, release version for the Nexus 6? What version are you on, today? If you are on 5.1 or higher, and you decide to downgrade, do not downgrade your bootloader, as it could brick your device.
https://developers.google.com/android/nexus/images
cam30era said:
There is only one legitimate site for Google factory images, and it's linked below. I don't understand why any provider would block it...
And why do you want 5.0? That is the original, release version for the Nexus 6? What version are you on, today? If you are on 5.1 or higher, and you decide to downgrade, do not downgrade your bootloader, as it could brick your device.
Click to expand...
Click to collapse
I've only had my Nexus for around 3 weeks and I've not updated from 5.0 yet.
Ducky10100 said:
I've only had my Nexus for around 3 weeks and I've not updated from 5.0 yet.
Click to expand...
Click to collapse
Doesn't matter. You've got NO OS now, so just flash the latest. If you're wanting to keep TWRP and dead set against flashing a ROM.zip from recovery as I've suggested, just flash the system and boot image from the factory images.
Can we get it done already?
danarama said:
Doesn't matter. You've got NO OS now, so just flash the latest. If you're wanting to keep TWRP and dead set against flashing a ROM.zip from recovery as I've suggested, just flash the system and boot image from the factory images.
Can we get it done already?
Click to expand...
Click to collapse
Yeah I've already done it now.
Ducky10100 said:
Yeah I've already done it now.
Click to expand...
Click to collapse
Awesome
Thanks for everyone's help!