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?
YES PLEASE POST QUESTIONS IN THIS THREAD RATHER THAN CREATING YOUR OWN "PLEASE HELP MY BRICK" THREAD
PLEASE READ AND RESEARCH FIRST AND THEN IF YOU MUST POST GIVE AS MUCH INFO AS POSSIBLE!Why am i making this thread? Aren't there already tons of them?
Exactly!
There are a couple a week and many times the old threads have already answered
all the questions needed to recover the brick, or explain why it cant be. So I'm here
to alleviate the clutter and hopefully help people more quickly.
Let's try to define a "brick"
People seem to say there is a "hard brick" and a "soft brick," to me that's just nonsense.
A brick is a brick. when you have no access to your recovery or your bootloader
then you have a brick. This is your phone wont turn on and it cant be recovered without j-tag equipment. (not for a novice)
Now you have no more than a brick on hand, or a pretty paperweight. What most
people have is a "soft brick" which really isn't a brick rather a phone that isn't
working as it should, but still a completely recoverable phone. A phone that doesn't
boot is just that, not a soft brick as it should be easy to fix and not to be used
as a paperweight. But i'll stop quibbling about the terms now as at least we
have an understanding.
A couple things first:
I implore you to read through a few threads on this as oh so many answers are there.
These are just a few from the last month or so!
HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE HERE
As apparent as it may seem to those who frequent this forum, clutter only lessens
the experience here. Many never read the forum rules or listen to the mods. I'm
not trying to be a **** here, but we do need to at least attempt to keep the threads
clean. I understand that there is a lot to sift through but i can assure everyone
that questions will be answered faster and more clear to those who at least attempt
to do a little homework... rant over, let's fix those bricks!
So your phone wont boot...
you will need to know a few things about your phone as will the people helping you.
Let's make a list of needed information...
1) Are you rooted? Which method did you use to obtain root?
Click to expand...
Click to collapse
Different methods of rooting can give a different outcome. Importantly having true
radio s-off or not, and with some methods (visionary) that could cause a brick in itself.
If you cant remember how you rooted thats fine, information given here will help.
2) Can you access either bootloader mode or recovery on your phone?
Click to expand...
Click to collapse
If you can, then chances are your phone can be fixed. If you don't know how to
get into these modes - simple way is to power on while holding volume down.
This is the bootloader (also known as Hboot or SPL - secondary program loader)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is an example of the screen
The important information to take out of here is the engineering DZ Hboot, radio
secure flags removed (s-off) and the 26.13.04.19_M radio (commonly .19 radio)
You can see it is in fastboot mode (in red) and to scroll up and down through the
options you use the volume rocker, selecting an option with the power button.
if you choose bootloader the screen will look like this:
Obviously some bootloaders will read different depending on radio, Hboot version,
including shipped verse engineering, s-on/off, etc. And I believe without an ENG
Hboot you don't get the system info option.
3) Write down everything you can on this screen, including *SYSTEM INFO*
if you have it and the output from *IMAGE CRC*
Click to expand...
Click to collapse
Please realize the more information the better, give everything but personal info,
really just the IMEI in the *SYSTEM INFO* option. (which really isn't all that personal) This leads to:
4) Which recovery do you have? Stock? Clockwork? 4EXT? Version #...
Click to expand...
Click to collapse
If you don't know, check!
5) What happened recently or just prior that may have cause this?
Click to expand...
Click to collapse
This may be anything to i was updating angry birds to i tried turning it on and it
wouldn't. If your answer is i dropped it in the toilet and just plugged it into an outlet
to dry, i cant help you to much...
6) Pull a logcat of the bootloop
Click to expand...
Click to collapse
If you're not sure how to pull a logcat HEREare some quick pointers. You will need the Android
SDK, and ADB.exe download in platform tools. THIS GUIDE will help setting up
fastboot and ADB, both are very helpful and needed tools for Android users
Pulling a logcat
Once you have ADB up and running open a command prompt (Linux and OSX users
will have different steps) where ADB.exe is located on PC by holding shift and right-
clicking in the folder > choose open command here. In CMD type:
Code:
adb devices
if you see your serial number then proceed, if not we need to troubleshoot.
Code:
adb logcat > logcat.txt
this will create a text file in the directory CMD is in named logcat.txt, you can name
the .txt what you'd like by changing the logcat.txt to whatever, maybe output.txt
now to stop it just hit (Ctrl + c) the control key and c key at the same time. Now
upload it to XDA, or put in code wraps, or post the link to the pastebin.
Code:
This is written in code wraps and [URL="http://pastebin.com/"]HERE YOU WILL FIND PASTEBIN[/URL]
***Please provide as much of this information as you can in your first post!***
What can i do to recover my phone already!
You are probably very frustrated right now, very understandable... please don't yell
at, or complain about, or blame your situation on those trying to help. No one is forcing
you to take the help given here and the last thing i want to hear is your complaints
about me/XDA/the world because your phone is toast and you need j-tag equipment.
Just wanted to get this out there, although its rare, don't blame others for your mistakes
or your misfortunes, thanks
Everyone has a unique situation! This is not a solve all for everyone!
Click to expand...
Click to collapse
Getting down to business...
Slowly lets work through the more obvious steps first, as simple as they seem to some,
it will fix most peoples problems. I will start by assuming you are rooted, those that
aren't i will add some more info....
First thing to do is to take out the battery.
Click to expand...
Click to collapse
What... well i said I'm starting slow. This is more for when a phone wont boot into
anything, no operating system, no recovery, no Hboot. If it does not, the first thing
to check is the battery. When you plug it in does the LED charge indicator come
on? Does the LED ever change to green? Have you tried different chargers? USBs?
Different batteries? It may be a hardware fault such as a bad USB port or charger.
I'm not going to spend more time on this case, but if you are finding yourself in this
situation, try a few things out first, if nothing works then feel free to post here and
I or some other helpful XDA member will attempt to troubleshoot more.
So your in a bootloop - rooted phones -
This is your phone gets past HTC/T-Mobile splash screen and gets stuck in the ROM's
boot animation. This tends to be most common issue for people new to android and
is very easily fixed. This may be caused by various things such as bad flash of the
ROM if its the first time booting into it. Maybe you adjusted DPI or overclocked too
much. Well, many possibilities, so first boot to recovery and wipe all (you will loose
personal info here) No matter the recovery you have (except stock) there are options
to wipe system, cache, dalvik, data. Do this, and while you are at it why not format
partitions, easy if in 4ext recovery. And for safe measure USE THIS SUPERWIPE
Or the AIO TOOL is proving to be great as well.
*If you would like you can always first try flashing the ROM or kernel first without
a wipe, or only wiping cache and dalvik, this may be a cure without loosing data*
After all this wiping and formatting we need to flash the ROM again. If you continually
have problems try a different ROM (something known stable) or a new download.
Every good ROM developer should have a MD5sum posted with their download. A
matching MD5sum will make sure what you flash will be what the developer uploaded
and didn't get corrupt when you downloaded it. GREAT MD5 TOOL FOR WINDOWS
And THIS ONE WILL ALSO CHECK SHA-1
If you are still getting a bootloop after all this then more info will be needed, post
here with your problem and all information you can give about your phone. Also if
you have ADB access then please post a logcat as well (pastebin or code wraps!)
Code:
This is written in code wraps, and [URL="http://pastebin.com/"]HERE YOU WILL FIND PASTEBIN[/URL]
If you don't know how to post a logcat then you didn't read the first post!
If your not sure you are doing any of the above correctly feel free to ask for more
details otherwise see THIS GUIDE for a better understanding
Stuck in a bootloop - not rooted-
You will have far less opportunities to fix this with an non-rooted phone. The first
thing you may want to try is boot into safe mode (hold 's' button on keyboard while
powering on. If this works then you more than likely have a malicious app, try and
remove the most recently installed or most recently updated.
If this wont work then we'll need to boot into Hboot (volume down while powering
on) Then choose factory reset. You will loose all data (except whats on SD card,
or whats stored in the cloud) This will be like the day you first got your phone.
If that doesn't help the last thing you can try is to flash the latest RUU (ROM Utility
Update) from HTC.COM or other options HERE as well.
Not all phones are made equal...
If you have ADB access through recovery it may be helpful to know what eMMC
you have. There were two different chips made for the vision; SEM04G and M4G2DE,
the latter being a chip prone to failure by no fault of the user.
open a command prompt anywhere on computer and type
Code:
adb devices
if you see your serial # then you have access to ADB, if not more troubleshooting needed
now continue on
Code:
adb shell
dmesg | grep mmc0
if the output is something similar to this:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Click to expand...
Click to collapse
Then chances are your eMMC is fried, dead, and unrecoverable. :crying: sorry
To test which chip you have, again in CMD type
Code:
adb shell
cat /proc/kmsg | grep 'mmc0:0001'
you should see an output ending in something like
mmcblk0: mmc0:0001 SEM04G 2.17 GiB
or
mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Other methods
This may work better for those with a working phone wanting to check theirs:
Code:
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
-this can be done via ADB or terminal with a working phone without booting to recovery-
I am under the impression, but haven't yet confirmed that the M4G2E (bad) chip is
made by Samsung while the SEM04G (good) chip is made by Sandisk. No guarantee
but you may be able to check this via fastboot:
Code:
fastboot oem check_emmc_mid
this should display either Samsung or Sandisk - if anyone can confirm this i would
be very appreciative!
*pulling a logcat or checking what eMMC you have will not recover any part of
your phone, just give more info about your phone and potentially help with the
troubleshooting process
*lots more to come, hopefully today or tomorrow!
More advanced measures
The previous post only suggests basic technology "fixes." While i don't consider factory
reset a fix, the outcome may be you have a working phone. These few things mentioned
above are just the first steps in recovering your brick, ALWAYS start with the basics
before moving on to more drastic measures as you can cause further damage. Of course
you may have to do this to recover your phone, my warning is to read up and ask questions!
Phone wont boot - no recovery
This is a bad sign, but in many cases flashing a new recovery via fastboot is all you need
to do. If you have an engineering SPL than proceed:
First do a test boot: boot phone into bootloader>fastboot mode>usb>open CMD
Code:
fastboot devices
See if your serial # comes up, if so proceed if not READ THIS (POST #3)
Code:
fastboot oem jump
Copy and paste the output, give it 5-10 minutes, if your phone sits at HTC splash then:
DOWNLOAD THIS RECOVERY to computer, extract the image noting the folder its in
Boot phone into bootloader>fastboot mode>usb>open CMD where recovery.img is
Code:
fastboot erase recovery
Note if there is an error or not
Code:
fastboot flash recovery recovery.img
If everything worked then:
Code:
fastboot reboot-bootloader
From here choose recovery, once rebooted go ahead and format all
*If you still cant boot into recovery post here!
Still i cant restore my phone!
Things are looking grim, but there still may be hope. If you have a working Hboot there
will always still be a chance. I always recommend ROOTING A PHONE RIGHT WHEN YOU GET IT
Even if your only reason is to recovery when things go bad, having an engineering
bootloader is just the cats meow. So unless your eMMC is fried, we should be able
to get you up and running again!
So fresh and so clean!
Wiping clean is great and formatting is even better. If you loose recovery access
it may be hard. Thankfully fastboot can help!
Code:
fastboot erase system -w
*I'm having trouble getting fastboot format and oem format commands to work,
I'll update this post when i see what the issue is.*
If you still have a working recovery do all wipes and formatting through it. Also try
and flash THIS SUPERWIPE SCRIPT and or THE AIO WIPE TOOL
When all is failing...
It is looking like you may have a fried chip, or at the very least some severely corrupt partitions.
An eMMC that has lost read/write capabilities we cant fix, not even with j-tag :crying:
But corrupt partitions can be fixed, usually by simply reformatting. I'm working on the
fastboot commands, but you can always reflash other partitions (like you did the recovery)
-----------------Always be careful flashing firmware!!---------------------
Click to expand...
Click to collapse
Check md5sums, and know what and why you are flashing, don't jump to this step
when you're in a bootloop!
HERE ARE SOME PC10IMG.ZIPS The post explains how to flash them trough your SPL
but you can open and extract the content and then flash through fastboot. Commands:
Code:
fastboot flash radio radio.img
This will give you the .19 radio only
Code:
fastboot flash hboot hboot_7230_0.82.0000_100902.nb0
This will give you the Desire Z engineering Hboot. *if you use the G2 one change the command
Code:
fastboot flash update PC10IMG.zip
This will the whole package (preferred over SPL flashing as any error will show in CMD)
*need to change command or change name of .zip
I'm not making this thread for :good: Thanks or 5star rating, I'm doing this to help out
others. XDA members have helped me so many times in the past that this is just one
of my small contributions. All i ask of you to be respectful and share what you learn
*Hope your up and running again soon!
i would define a brick as something used to build a house..... i would describe my phone that wasn't working as a broken phone
thanks for the information that's really help full..:angel:
Everyone has a unique situation! This is not a solve all for everyone!
Click to expand...
Click to collapse
So is this a good place for solving unique situations? .. or should I start a new thread somewhere else?
I've tried to bric this thing a thousand times by all the various good posts in the forums. cant seem to get into recovery or flash new one, maybe hardware is bad?
have access through fastboot & PC10IMG, but not adb. comes back to reboot-loop, maybe recovery partition is bad?
eng hboot s-off ... kinda noob, but.
and dont want to interupt the flow of your page here, either. thanks
Not at all a disruption, this is why I'm making the thread. I want everyone who has a nonworking phone to have an easy place to share their problems and hopefully find a fix.
Haven't finished all the info in the first few posts but I hope to have many solutions covered there and if not people can dig through this one thread, instead of dozens, to find the answers they need
So on to you situation
Can you get into bootloader? I assume so being you said you have fastboot but no adb. (By the way you should have adb access in recovery) can you write down all the info I'm requesting in the op about your phone please, this will help expdiate your fix if there is one
Sent from my HTC Vision using xda premium
I can get into bootloader, but not recovery. I was able to access the stock recovery once. i'll work on the rest of the info ..
meantime, anyway to confirm good/bad hardware, eMMC? i would hate for the past week to have all been on a fried chip.
If you had adb working then you can check which emmc you have, there is one prone to failing. Also you can check system info in hboot. For now your best bet is to flash a new recovery via fastboot. I will be adding this in the first few posts when I get a moment
http://forum.xda-developers.com/showthread.php?p=27796375
See post 3
I would appreciate if you can post the information in the op as it will determine if you can even flash a recovery via fastboot or if other steps need to be taken rather then just me guessing on what to do next, the more info you can give in your first post the less questions I will have to ask making less clutter in this thread
Sent from my Nexus 7 using xda premium
yeah great. thanks
i have tried to flash new recovery multiple times .. it seems to take, but then i can never get into it, just back to reboot-loop. i have also seemingly been able to flash radio, hboot, partitions .. all via fastboot - cant get adb.
vision pvt eng s-off
hboot 0.84.2000
microp 0425
radio 26.03.02.26_m
eMMC boot
sys info:
sn 123456789
lcd so
touchpanel atmelc12_20aat
commit adbd7a75
os ver. 1.19.531.1
imei 123456789
cid 11111111
eMMc sandisk 2152 mb 4407295 sectors
image crc:
hboot 0x2a125cf4
boot 0x1b87420d
recovery 0xd4af6ad9
system 0x749ce305
#some of this has changed periodically as i've flashed this and that and back again multiple times
i have tried flashing two different CWM recoveries and the EXT_4 as well, no luck.
i seems to be able to flash different hboots at will.
at one point after other things didn't work, i ignored the 'Warning' and flashed a PC10IMG stock, which gave me the ship hboot, still s-off ..
i have tried flashing ROM.zip's directly, including CM7 and stock gingerbread - no luck. done lots of wipes.
"word is .." (not my phone) this trouble came after trying to update CM? maybe something about firmware??
not sure about root - i assume i have it, but no idea what method was used originally to root, etc
at this point i've tried what i know and it seems beyond me <am a hobbyist>, so i'm looking for some insight as to what might be going on - if it's worth still trying to fiddle with it or if it's for target practice ..
thanks for the thread.
When you say your trying to flash cm7 directly are you flashing it as an update via fastboot? Do you have any old nandroid backups made in yaffs2? If you do you can flash the images in fastboot and see what happens
It sounds as if the recovery partition is severely corrupt, but it is strange that flashing through fastboot doesn't give an error. Without adb it makes it hard to test a few things but I have a couple more ideas you can try, I need to check a couple things out and when I get home ill post back
Sent from my HTC Vision using xda premium
i have tried flashing various ROMs, cm7 included, various ways -- as update, as zip, as pc10img.
no backups for this devices. maybe i can steal files from another device?
i have got various fastboot errors, though usually seems to flash mostly.
when i erase cache, for example, i get .. erase complete, but no auto format
i tried flashing a recovery again and get no error msg.
well you cant flash backups made from a different model but another dz\g2 will work fine,
if i get a second ill tray and dig a few up for you.
try to record any error you get through fastboot though
looking at your system info you show:
eMMc sandisk 2152 mb 4407295 sectors
i believe the "bad" emmc shows a
emmc samsung - for the bad chip and
emmc uknown - if its completely fried
there may be a fastboot oem command to confirm what chip you have, ill test on this
being you have already flashed a pc10img.zip why dont you go ahead and flash ONE OF THESE
only difference is one has g2 engineering hboot and the other dz, both come with a 4ext touch recovery rc
try flashing through fastboot not hboot though, this way we can get the errors if any
demkantor said:
why dont you go ahead and flash ONE OF THESE
Click to expand...
Click to collapse
Code:
[email protected]:~$ fastboot flash zip /home/simon/Downloads/PC10IMG/DZ_PC10IMG.zip
sending 'zip' (17811 KB)...
OKAY [ 3.074s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) start image[radio] unzipping for pre-update...
(bootloader) start image[radio] flushing...
FAILED (remote: hboot pre-update! please flush image again immediately)
finished. total time: 34.219s
[email protected]:~$ fastboot flash zip /home/simon/Downloads/PC10IMG/DZ_PC10IMG.zip
sending 'zip' (17811 KB)...
OKAY [ 3.070s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) start image[tp] unzipping & flushing...
(bootloader) start image[tp] unzipping & flushing...
(bootloader) start image[rcdata] unzipping & flushing...
OKAY [ 26.993s]
finished. total time: 30.063s
[email protected]:~$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.159s]
finished. total time: 0.159s
[email protected]:~$ fastboot reboot
rebooting...
comes up to white HTC screen, buzzes once, flashes off, back to reboot-loop. something is not right :cyclops:
what does it say on hboot screen now? anything change?
also just a thought, have you tried hitting factory reset from booloader, this also should boot you into recovery, if choosing recovery wont get you there i doubt this will but just a thought.
if you want you can always try the latest ruu through fastboot, may risk loosing fastboot commands afterwords though
the radio changed - back to the .19 radio
tried reset from bootloader - same business
i did try a newer ruu (not sure about newest?) - got the new stock bootloader, radio. i would like to try the ruu.exe from htc, but i am not on a windows machine and wine is out of date for debian stable ..
i wonder about some things:
is it possible to rewrite the misc.img from fastboot?
a way to have boot ignore the recovery partition?
abandon android all together and install a native linux?
well im thinking the issue maybe deeper as technically you could erase the recovery and still boot into an os so there is something even worse going on here. there is some sort of read/write issues with the emmc but what im not exactly sure
as for removing android and booting a linux distro... yes and no. you can do it if you had a working os being that you can run debian or ubuntu under chroot, like a virtualbox
there maybe a way and im sure there are some threads hear on xda, but if you cant get android running i dont think you will get anything else running.
you can always try logging onto #G2ROOT @ FREENODE and see if someone has any ideas in real time
edit:
another thought, when you flash a new recovery via fastboot does it give a message like "okay.... finished... total time..."
or does it just flicker?
if you get the message likes its complete maybe there is a chance it is being flashed to the nand but something else is keeping you from rebooting to it.
the earlier clockwork recoveries used to have a bug, when you plug your phone in
with the phone powered off, it would auto boot to recovery. just looked at another thread
and someone there had this happen with a cw touch recovery, (only ever heard of it happening with older recoveries before)
but maybe try flashing an one like THIS ONE and see what happens
thanks for the help and ideas ..
i have tried flashing the older recoveries, but may try again. and when i do, i get all the good messages - "okay.... finished... total time..." etc.
some sort of read/write issues
Click to expand...
Click to collapse
I remember reading in the 'Warning' post that if the stock image gets flashed on top of root/s-off that there is a conflict of version number or something to do with misc_img or wpthis.ko business. i think i will try back to that thread and the downgrade firmware thread to see what of that i can do from fastboot.
at this point i dont have much to lose, so i'm open to experimenting some. like i said in OP - i've tried to bric this thing a thousand ways :fingers-crossed:
edit.
i've just tried a buunch of different thing with no change. am having to assume it's hardware, maybe not worth much xtra time now - but for with the screwdrivers ..
try and see if you can get into fastboot RUU mode?
Code:
fastboot oem rebootRUU
from here you can try to do a complete install of original ROM, radio, recovery etc.
i don't know how much help you will have with this but before you use your phone to build a wall...
BE CAREFUL WITH THESE
if it doesn't work you may end up with nothing... not much different then you have now
if it does seem to finish
Code:
fastboot reboot-bootloader
see if you can access recovery now?
demkantor said:
try and see if you can get into fastboot RUU mode?
Code:
fastboot oem rebootRUU
from here you can try to do a complete install of original ROM, radio, recovery etc.
i don't know how much help you will have with this but before you use your phone to build a wall...
Click to expand...
Click to collapse
this is what i was doing yesterday - no luck
BE CAREFUL WITH THESE
if it doesn't work you may end up with nothing... not much different then you have now
if it does seem to finish
Code:
fastboot reboot-bootloader
see if you can access recovery now?
Click to expand...
Click to collapse
these are all windows.exe - i dont have access to a machine to extract the rom.zip ..
i did do this all once a week ago and i think i remember being able to get to the stock recovery at one point, but was not able to repeat that yesterday.
edit
i will try this again - these RUUs are newer than the one i had - at this point i would be happy with stock because this is a nice device otherwise. think i'll open up the back too and see what kind of squirrel is living on the board.
any chance it's possible to boot directly from SD?
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick
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!
After using the megapixel rom. I tried flash back to stock with root tool kit.
During the process it told me I had to manual boot in recovery to a factory restore. That would not work so I ended up soft bricking my phone. I was able to side load twrp and the latest build and flash it (thank god). No when I do oem lock boot loader, my nexus 6p won't boot. As soon as I oem unlock, it will boot. Any ideas what could be cause that?
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
This is a perfect time to remind folks that "locking" the bootloader is something that should be done with great care. There are dozens, if not hundreds of "my phone is bricked" threads centered around locking their bootloader without understanding the requirements and risks. If you don't have a reason to do it, leave it unlocked. If I need to do it, I flash 100% back to stock using a full factory image before locking.
Sent from my Nexus 6 using XDA-Developers Legacy app
BostonDan said:
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
Click to expand...
Click to collapse
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Blackfish77 said:
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Click to expand...
Click to collapse
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
You should only lock bootloader when you are on stock factory image from nexus developers site. Either use flash_all script or flash everything manually. As others said keep away from toolkits.. You never know what can go wrong or what they re doing in background.
As I understand you restored TWRP and Megapixel rom and tried to lock the bootloader when you had that combination installed on your phone? That can not be done. You are either full stock (rom, kernel, recovery...) and locked bootloader or unlocked bootloader and any combo of kernel, rom, recovery that you want.
RoyJ said:
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
Click to expand...
Click to collapse
I ended up using fastboot to flash factory. I then re locked bootloader and everything booted without and issue. I was happy about that. I re rooted and everything is working great. :good:
I can say I learned a lot from this experience. Thanks to everyone for your advice. I am now comfortable using the fastboot method. Almost bricking my phone was scary but it taught me a lesson. Cheers everyone.