Related
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
jimmydafish said:
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
Click to expand...
Click to collapse
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
minitele said:
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
Click to expand...
Click to collapse
you should join the G+ community for much better and more pointed help. The forums get cluttered.
1) download correct 4.2.2 (57-1) FXZ file
2) extract boot, system, recovery from the file
3) fastboot flash each of the partitions to your phone
(fastboot flash boot boot.img)
(fastboot flash recovery recovery.img)
(fastboot flash system system.img)
Doing this will put your phone in a state where it is ready to update.
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
jayboyyyy said:
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
Click to expand...
Click to collapse
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
jimmydafish said:
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
Click to expand...
Click to collapse
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
jayboyyyy said:
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
Click to expand...
Click to collapse
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
minitele said:
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
Click to expand...
Click to collapse
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
jayboyyyy said:
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
Click to expand...
Click to collapse
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
minitele said:
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
Click to expand...
Click to collapse
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
jayboyyyy said:
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
Click to expand...
Click to collapse
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
minitele said:
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
Click to expand...
Click to collapse
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
tracyde said:
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
Click to expand...
Click to collapse
To all,
The forums and people in our arena never fail, fastboot erase cache worked perfect. I have recovered all my data and now I will definitely continue to performing a full recovery with stock image.
Thank you again all for all of your help, I am glad to see at least this corner in the internet still is alive and kicking!
Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"
First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??
Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Enthusiast09 said:
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Click to expand...
Click to collapse
Sorry to hear about that. I had the same problem with my modded 6p and had a full backup on my pc and was still under warranty so it worked out fine for me. Unfortunately for you you are most likely not going to be able to fix it even from wiping it. I had the same problem and because I had an unlocked bootloader I was able to do much more than you could with flashing stock images. If you can't enter recovery then you most likely have a brick and can't fix it. I'm not sure if there is a way via adb and fastboot commands with a locked bootloader to retrieve data but I'll let you know ow if I find one. What kind of data do you have? Google usually syncs things like your photos and apps downloaded will be saved in the google play store. I hope this helped?
DEVILOPS 007 said:
Sorry to hear about that. I had the same problem with my modded 6p and had a full backup on my pc and was still under warranty so it worked out fine for me. Unfortunately for you you are most likely not going to be able to fix it even from wiping it. I had the same problem and because I had an unlocked bootloader I was able to do much more than you could with flashing stock images. If you can't enter recovery then you most likely have a brick and can't fix it. I'm not sure if there is a way via adb and fastboot commands with a locked bootloader to retrieve data but I'll let you know ow if I find one. What kind of data do you have? Google usually syncs things like your photos and apps downloaded will be saved in the google play store. I hope this helped?
Click to expand...
Click to collapse
Yeah I've tried countless things but it all comes down to me not being able to access recovery. Please do let me know if you do find one thanks . I have some very important docs as well as images in it that I need it badly . I disabled that sync feature as it took very long (for me) to back up all the media. Guess it was a big mistake ....
Enthusiast09 said:
Yeah I've tried countless things but it all comes down to me not being able to access recovery. Please do let me know if you do find one thanks . I have some very important docs as well as images in it that I need it badly . I disabled that sync feature as it took very long (for me) to back up all the media. Guess it was a big mistake ....
Click to expand...
Click to collapse
If you had USB debugging enabled then try this
https://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
DEVILOPS 007 said:
If you had USB debugging enabled then try this
https://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
Click to expand...
Click to collapse
I don't , its off by default ? I took a look at that page and tried it , when I fastboot devices , it can detect , but when I adb devices the list is empty .
I'm experiencing boot loop also. It won't boot into recovery. Only bootloader. I'm completely stumped.
Enthusiast09 said:
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Click to expand...
Click to collapse
Bootloop here too
Just tried to upgrade 7.1.1 (unlocked usb debugging enabled) to 7.1.2 using Skipsoft Toolkit. Upon reboot, it just keeps going thru the graphic animation. When I connect it it says 7.1.1 detected.
I am going to try again to upgrade it. Seems like it's working. problem is it says detected system is 6.0.1 now.
Hey, it also says it takes a while for the first boot, so I may have gotten all 21st century and impatient on it.
I also tried a factory reset after freaking out that I had laid a brick...
At least with the skipsoft toolkit I was able to communicate with it!
Here's hoping!
---------- Post added at 04:51 AM ---------- Previous post was at 03:56 AM ----------
Well, although I can get to twrp, I am unable to do anything else. I can't find any clues that are up to date and it's a bummer
Didn't need to be a TWRP expert; just booted into recovery mode, selected the latest factory stock image and flashed it. back to a working nexus 6p and all i gotta do is re-root it, edit the build.prop to enable wifi hotspot (I'm on ATT) and all is groovy. Muchos props to mark and skipsoft toolkit!
Yesterday I also got a bootloop. My smartphone hovered and went into reboot. So it did not boot. It reboots. In the recovery he does not go.
Same here but with stock recovery
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Thanks
morelo said:
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Click to expand...
Click to collapse
Yes. If you haven't wiped/factory reset yet, you can load a newer OTA image from Recovery. Same or older OTA will not work. Set the device to update from ADB and then send it from PC. If you have wiped the phone, obviously the OTA won't work. This will work with a locked bootloader and no usb debugging enabled.
morelo said:
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Thanks
Click to expand...
Click to collapse
You could maybe try this ?
https://www.reddit.com/r/Nexus6P/comments/66wsvq/this_might_sound_absurd_but_i_just_fixed_my_nexus/
Please try this if you need to boot it and get your files off the phone, it worked for me and I was able to backup my pictures.
https://www.reddit.com/r/Nexus6P/comments/66wsvq/this_might_sound_absurd_but_i_just_fixed_my_nexus/
Hi, I've come to these forums because you guys are knowlegeable.
I essentially uninstalled thorugh ADB the package installer (com.google.android.packageinstaller) and little did I know that was a big mistake on my part, as I didn't realize the package installer was a core part of the system. All was going well until i turned on and off my phoen, and it is now always stuck in recovery mode.
- Rebooting the phone just sends me back to the menu.
- I've not tried wiping the data yet, since I want to keep my files (for the moment).
- Connect with MiAssistant allows me to connect my phone to my PC, but it in sideload mode automatically. I can go in fastboot mode though, and fortunately I have turned USB Debugging on.
As I've come to realize, a factory reset or flashing a ROM would fix my issue, but also delete all my files (photos, music...). I was planning to do a backup of my photos, but now it's too late.
Is there any way I can access my files and pull them to my PC on sideload/fastboot mode?
The only thread i have seen with a similar problem is this one: https://forum.xda-developers.com/sho....php?t=2487147
I also get the error:closed when I try an adb pull.
Thanks in advance.
guembo said:
....I essentially uninstalled thorugh ADB the package installer (com.google.android.packageinstaller) and little did I know that was a big mistake on my part, as I didn't realize the package installer was a core part of the system. All was going well until i turned on and off my phoen, and it is now always stuck in recovery mode.....
Click to expand...
Click to collapse
You have omitted some core information from your writeup:
1. Is your bootloader unlocked?
2. Which version of MIUI are you running?
3. Which recovery are you using?
One might hazard a guess about these questions, but that would not be a sensible basis for proposing possible solutions.
DarthJabba9 said:
You have omitted some core information from your writeup:
1. Is your bootloader unlocked?
2. Which version of MIUI are you running?
3. Which recovery are you using?
One might hazard a guess about these questions, but that would not be a sensible basis for proposing possible solutions.
Click to expand...
Click to collapse
1. My bootloader was locked.
2. MIUI Global 11.0.8
2. Recovery 3.0
I realized having the bootloader meant it was pretty much impossible to get my data back. I've been searching for answers for the past 3 days and honestly my patience just ran out.
Decided to just factory reset the phone and that's that.
Thank you for your willingness to help me though. Appreciated.
guembo said:
1. My bootloader was locked.
2. MIUI Global 11.0.8
2. Recovery 3.0
I realized having the bootloader meant it was pretty much impossible to get my data back. I've been searching for answers for the past 3 days and honestly my patience just ran out.
Decided to just factory reset the phone and that's that.
Thank you for your willingness to help me though. Appreciated.
Click to expand...
Click to collapse
Unfortunately, with a locked bootloader, the options are limited.