Related
I've been searching for hours here but can't find a solution that works...
My wife's Wi-Fi Nexus 7 (running stock, unrooted) suddenly got stuck in a boot loop during the white Google logo (never gets to the Nexus "X" animation). I figured I'd simply restore to stock through fastboot/adb.
The problem is when I try to unlock the bootloader (which is needed to be able to flash the factory image) I get this error message:
Code:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
[COLOR="Red"][B]FAILED (remote: ()[/B][/COLOR]
finished. total time: 2.736s
Because of this, I can't go any further. I can't flash anything because it tells me I need to unlock the bootloader. I tried a couple of different toolkits with the same results.
I get fastboot access, and the device is listed when I type "fastboot devices" but I don't get adb access. When I type "adb devices" I simply see:
Code:
>adb devices
List of devices attached
...and nothing else. No devices listed. If I try other adb commands, I get "error: device not found".
I've tried installing the Google drivers as well as other USB drivers from toolkits. No change. But I can send it commands through fastboot fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can get into recovery, but can't flash anything. I am able to factory reset from recovery, but it doesn't help. The tablet just keeps boot-looping.
Am I screwed? Any ideas? Thanks in advance to anyone who responds
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
bigdaddy619 said:
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
Click to expand...
Click to collapse
What's PTP mode? Were you having the same issue I'm having?
The thing is my tablet is getting recognized, at least in fastboot. Just not in adb but I'm thinking that's because it never had debugging turned on.
Wrong input.
grisoxxl said:
If you can acces recovery make full wipe.
Click to expand...
Click to collapse
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
ecaggiani said:
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
Click to expand...
Click to collapse
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Sent from my Nexus 7 using xda premium
ganeshp said:
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Click to expand...
Click to collapse
That's what I'm trying to do! The guides I've seen have me unlock the bootloader to be able to flash stock firmware. Can you point me to a guide? Is there an RUU maybe?
ecaggiani said:
Am I screwed?
Click to expand...
Click to collapse
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
ecaggiani said:
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
Click to expand...
Click to collapse
Hi, im having the exact problem you're having, did you end up contacting ASUS? how was your experience like? Did you get it resolved? I think I voided my warranty by trying to pull the battery ):
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s
your help please?
regards
Ricey
Ricey_uk said:
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s.
your help please?
regards
Ricey
Click to expand...
Click to collapse
Hi, Ricey_uk...
Mmm... not sure, but I think you're trying to flash the wrong factory image for your device...
Reason being, is because (QUOTE: fastboot flash bootloader bootloader-tilapia-4.13.img) 'tilapia' refers to the 3G/GSM variant of the Nexus 7.
But you appear to have a (QUOTE: (bootloader) product: grouper) 'grouper' device. Which is WiFi only... this seems to be supported by the two lines in your output...
(bootloader) version-baseband: N/A
(bootloader) version-cdma: N/A
... which suggests your N7 has no 'radio' capability.
You need the factory stock image for "nakasi" for Nexus 7 Wi-Fi only (device board "grouper").... NOT "nakasig" for Wi-Fi & Mobile (device board "tilapia").
(See my sig for download links).
-----------
In short, there is an incongruity/contradiction in your reported outputs.... the device is either 'grouper' or it's 'tilapia'
It can't be both.
If it has a SIM card (like a mobile phone), or a space for a SIM card, then it's 'tilapia'... if it doesn't, then it's 'grouper'.
Ensure you are flashing the correct factory stock for your device.
-----------
But having said all of that... (and if there is confusion, it needs to be cleared up)... it doesn't explain why something as straightforward and innocuous as...
Code:
fastboot oem unlock
...isn't working.
Two possibilities occur to me...
1) A bad USB connection. Try a different USB port on your PC... Or, maybe, a different USB cable.
Once the fastboot oem unlock command is issued at the PC end, it will need to be confirmed at the Nexus 7 end (see attached thumbnail). Use either of the two VOL buttons to choose YES and confirm by pressing the POWER button.
2) It's possible there could be a hardware failure... some problem with the EMMC flash memory chip. As alluded to by a previous poster...
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Whilst I don't discount the possibility that it COULD be EMMC chip failure, I'm not inclined to think that this is a likely possbility. More prosaic explanations need to be explored first.
First... check the integrity of of your USB connections - at both ends; change to different USB ports on your PC; if you can, try a different PC; try a different USB cable. And confirm at the Nexus 7 end, once the unlock command has been issued. (again, see attached thumbnail).
Second... if you are going to try to fastboot flash back to Android factory stock... make sure you do so with correct version for your device. If you're device is Wi-Fi only, you need the 'grouper' version... if not, the 'tilapia' version.
Hope this helps.... and good luck.
Rgrds,
Ged.
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Ricey_uk said:
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Click to expand...
Click to collapse
Hi, Ricey_uk...
Yeah... that, unfortunately, does not sound good at all. Unlocking the bootloader just sets some 'flag state' on the internal EMMC flash chip. Specifically, somewhere in the mmcblk0boot0 partition, where the bootloader lives.
There's some technical info here... http://forum.xda-developers.com/showthread.php?t=2068207
If fastboot oem unlock is performing as you describe, then it strongly suggests some sort of hardware failure. It just shouldn't behave that way... once you have confirmed the oem unlock request on the Nexus 7, the PC should display (if I remember correctly), the following...
Unlocking....
The device is unlocked now...
The whole procedure should take no more than a few seconds. Blank screens and forced reboots have happened many times on my Nexus 7... but never whilst unlocking the bootloader (and yes, I have locked and relocked several times, when I was experimenting with the 'motochopper' root exploit).
----------------------------------
Incidentally, you won't find 4.13 on the factory downloads page, as that number refers to the bootloader version for JellyBean 4.2 and 4.2.1. (It's not always the case that with each new version of JellyBean the bootloader is updated).
Anyway... looking through my collection of system images on my laptop, I find the following...
JellyBean 4.1.2 -> bootloader-grouper-3.41.img
JellyBean 4.2.0 -> bootloader-grouper-4.13.img
JellyBean 4.2.1 -> bootloader-grouper-4.13.img
JellyBean 4.2.2 -> bootloader-grouper-4.18.img
JellyBean 4.3.0 -> bootloader-grouper-4.23.img
With JellyBean 4.3 being the latest, and it updating the bootloader to 4.23.
If you're still stuck on bootloader version 4.13, then that means it was last updated with the rollout of JellyBean 4.2, sometime around November 2012.
----------------------------------
All of which is technically interesting... but probably doesn't help you.
I think there is a hardware problem on your Nexus 7, that is preventing the bootloader-lock-state flag from being correctly set.
Wish I could be of more assistance.
Rgrds,
Ged.
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Ricey_uk said:
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Click to expand...
Click to collapse
Give me half an hour or so, and I'll upload it to my dropbox and I'll post a link. Gotta get it of my laptop first.
Although I'm not convinced it will solve your problem... but I suppose you have nothing to loose by trying.
Rgrds,
Ged.
---------- Post added at 12:53 PM ---------- Previous post was at 12:21 PM ----------
OK... here is the bootloader .img file - v4.13... extracted from nakasi-jp40d-factory-6ac58a1a.tar... or in English, Jellybean 4.2.1.
https://dl.dropboxusercontent.com/u/37483979/bootloader-grouper-4.13.img
Code:
File size: 2.05 MiB (2,146,892 bytes)
MD5: a119629c89ad06c7e49bebd260df9cf3
SHA-1: fd60a0d9da5c814e2c1ee049f537700cbbe2c3cc
Flash as follows....
Code:
fastboot flash bootloader bootloader-grouper-4.13.img
---------------
Be careful with this.
Flashing a bootloader is the riskiest single operation you can undertake on the Nexus 7.
All it takes is one false step, and you have a hardbrick.
The device will never boot again.
Make sure you have good USB connections at both ends... and before flashing... type...
Code:
fastboot devices
If you don't see a serial number, you have either a driver problem OR a possible dodgy USB connection.
Do not proceed with this flash until you see a serial number.
Normally, I would suggest test flashing something innocuous first, like a recovery, for example.... but since your bootloader is locked, that's not possible.
I'm not even sure flashing a bootloader is possible with a locked bootloader... but then, I've never directly flashed a bootloader before.
Very best of luck - really hope this fixes your problem.
Rgrds,
Ged.
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Ricey_uk said:
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Click to expand...
Click to collapse
Damn... thought that might happen... but wasn't 100% sure.
You can't use fastboot with a locked bootloader, even to flash a bootloader... and you can't unlock it because - well, who the hell knows why (but I suspect a problem with the internal EMMC).
What is the precise current status of your Nexus 7?
Android version?
Rooted?
Stock or Custom ROM/kernel?
Custom recovery (CWM/TWRP) installed?
Did you receive any OTA notifications regarding the recent release of Android 4.3? and if so did you allow the OTA update to proceed? What happened?
Rgrds,
Ged.
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Ricey_uk said:
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Click to expand...
Click to collapse
You can get the Android version info by going to SETTINGS>>ABOUT TABLET.
Without further details, what is odd about your predicament is this...
If your bootloader is v4.13, then that means the device hasn't been updated since November of last year. Since then, there have been, I think, 3 official updates from Google... the most recent being JellyBean 4.3 about a couple of weeks ago
Normally, when an OTA update is pending, you get pestered endlessly with an endless stream of notifications.
Upon the user accepting the lastest update (whatever that might be - but is currently JellyBean 4.3)... the device downloads the OTA, runs a checksum test on the current files in /system... and then'patches' them, meaning it brings them up to date.
The very last thing the OTA does is update the bootloader, by dropping BOOTLOADER.RAW into the USP(staging) partition. Upon automatic reboot, the new bootloader is then copied (from the USP/staging partition) into the bootloader partition proper... thus obviating the risks associated with flashing the bootloader partition directly.
Since November, the bootloader has been updated by this means twice... 4.13->4.18 (in, I think February, when JellyBean 4.22 was rolled out) and just recently 4.18->4.23 when JellyBean 4.3 was rolled out.
It's odd you haven't received any notifications of any OTA updates.
----------------------------------
Anyway.... A possible workaround...
A slightly rhetorical question... why do you want to unlock the bootloader anyway?
I assume it's because you want to root... or maybe flash a custom ROM...
That 'might' still be possible...if you're running a version of Android THAT ISN'T JellyBean 4.3, you can root via 'exploit'.
Details here - http://forum.xda-developers.com/showthread.php?t=2233852
This requires no fastboot commands and thus, no need for an unlocked bootloader.
It's really simple to implement. Indeed, I ran my Nexus 7 for several month BOOTLOADER locked, but rooted.
(But with the advent of JellyBean 4.3, root exploits no longer work.... so I've had to root the old fashioned way).
But it might be useful to you...
Anyway... once you are rooted, you can then flash a Custom Recovery... like CWM or TWRP.
Normally this would be done via fastboot. But there are two great apps available that will 'write' a recovery partition... directly from the Nexus 7.
These are Flash Image GUI and Flashify.
Both will request root access.
It doesn't matter which one you use, as they essentially do the same job... but IMHO, Flashify is the better of the two.
Once you have a Custom Recovery installed, the metaphorical gateway is open to whatever Custom ROMs or Custom Kernels you like.
----------------------------------
It's possible none of the above will work... maybe for the same reason why you can't unlock the bootloader. A suspected fault with the internal EMMC chip.
But it just might... and it's gotta be worth a shot.
To summarize
Root via 'exploit'
Use Flashify or Flash Image GUI to install a Custom Recovery
Good luck.
Rgrds,
Ged.
hi, i have an annoying problem with my razr m phone and i had spent about 8 hr on internet finding solution for my prob and nothing worked at all
here is my problem :
my nephew installed some app on my phone that required an update sometimes. but after last update, my phone got restarted and after that it stuck on droid eye logo that keep animating and nothing happened even i wait 2 hr s or more.
here is what i have done so far:
1. i got to recovery and use wipe data and nothing happened. but after i use wipe cache, my phone wont show complete message and my phone will restart.
2. i have downloaded 3 different stock rom's for my droid razr m from droid developers , and if i use rsd lite (i have downloaded 2 last versions), it got me error on first step, even i've download customised xml or remove those lines that prevents updating. and if i copy zip file and go to recovery, it says installation aborted.
3. i even try flash system.img using fastboot , and that gives me the error about the size of my file and wont let me write system.img.
4. next i've decided to unlock my bootloader but it got me 0x02 satus that according to motorola forums it is unlockable and so i cant update recovery or root or install custom roms.
and now i'm done. im really really dont know what to do with this phone. pleassse somebody help me.
thanks
abadgamer said:
hi, i have an annoying problem with my razr m phone and i had spent about 8 hr on internet finding solution for my prob and nothing worked at all
here is my problem :
my nephew installed some app on my phone that required an update sometimes. but after last update, my phone got restarted and after that it stuck on droid eye logo that keep animating and nothing happened even i wait 2 hr s or more.
here is what i have done so far:
1. i got to recovery and use wipe data and nothing happened. but after i use wipe cache, my phone wont show complete message and my phone will restart.
2. i have downloaded 3 different stock rom's for my droid razr m from droid developers , and if i use rsd lite (i have downloaded 2 last versions), it got me error on first step, even i've download customised xml or remove those lines that prevents updating. and if i copy zip file and go to recovery, it says installation aborted.
3. i even try flash system.img using fastboot , and that gives me the error about the size of my file and wont let me write system.img.
4. next i've decided to unlock my bootloader but it got me 0x02 satus that according to motorola forums it is unlockable and so i cant update recovery or root or install custom roms.
and now i'm done. im really really dont know what to do with this phone. pleassse somebody help me.
thanks
Click to expand...
Click to collapse
Post complete text on AP Fastboot screen.
Sent from my XT1028 using Tapatalk
You need to flash the system.img with 'mfastboot' not 'fastboot'.
Mfastboot has been modified to handle large .img files.
Sent from my XT1031™
ATTACK said:
You need to flash the system.img with 'mfastboot' not 'fastboot'.
Mfastboot has been modified to handle large .img files.
Sent from my XT1031™
Click to expand...
Click to collapse
hi
it says:
C:\android>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'system' (30720 KB)...
OKAY [ 2.359s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 2.609s
sd_shadow said:
Post complete text on AP Fastboot screen.
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
hi
AP Fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 02:30:05)
eMC Info: Size 8GB
Device is LOCKED, Status Code: 0
abadgamer said:
hi
it says:
C:\android>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'system' (30720 KB)...
OKAY [ 2.359s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 2.609s
hi
AP Fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 02:30:05)
eMC Info: Size 8GB
Device is LOCKED, Status Code: 0
Click to expand...
Click to collapse
It failed because your battery is low. The battery needs to be at least 50%. Charge it for a few hours and try again.
Sent from my XT1031™
ATTACK said:
It failed because your battery is low. The battery needs to be at least 50%. Charge it for a few hours and try again.
Sent from my XT1031™
Click to expand...
Click to collapse
Also I think kernel date is July 29, 2014...
rahimali said:
Also I think kernel date is July 29, 2014...
Click to expand...
Click to collapse
Yes, your bootloader cannot be unlocked.
Sent from my XT1028 using Tapatalk
ATTACK said:
It failed because your battery is low. The battery needs to be at least 50%. Charge it for a few hours and try again.
Sent from my XT1031™
Click to expand...
Click to collapse
it had 91% charge and every time i go to fastboot menu, it says battery low
rahimali said:
Also I think kernel date is July 29, 2014...
Click to expand...
Click to collapse
sd_shadow said:
Yes, your bootloader cannot be unlocked.
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
yep. if mfastboot wont work, i dont know what to do.
abadgamer said:
it had 91% charge and every time i go to fastboot menu, it says battery low
yep. if mfastboot wont work, i dont know what to do.
Click to expand...
Click to collapse
Hmmm....
Did you have any issues before your device went into bootloop? Any app crashes? Any abnormal behavior?
Do you remember the name of the app, that you believe, to be the cause of this issue?
Have you tried to erase userdata with mfastboot?
Code:
mfastboot erase userdata
Have you tried to flash stock firmware with House of Moto?
Stock firmware link:
motofirmware.center
Sent from my XT1031™
abadgamer said:
it had 91% charge and every time i go to fastboot menu, it says battery low
Click to expand...
Click to collapse
I suspect the battery is low and to 90% reading you were seeing was incorrect.
the battery could have also failed.
I would try to charge, if it does not boot to charge mode, you may need a fastboot cable and/or a new battery.
yep. if mfastboot wont work, i dont know what to do.
Click to expand...
Click to collapse
as long as ap fastboot says low battery you can not flash.
What is a Fastboot Cable
ATTACK said:
Hmmm....
Did you have any issues before your device went into bootloop? Any app crashes? Any abnormal behavior?
Do you remember the name of the app, that you believe, to be the cause of this issue?
Have you tried to erase userdata with mfastboot?
Code:
mfastboot erase userdata
Have you tried to flash stock firmware with House of Moto?
Stock firmware link:
motofirmware.center
Sent from my XT1031™
Click to expand...
Click to collapse
thanks man. i've dissapointed about this phone. but when i tried again today and used house of moto 4.2, it had did the trick and finally my razr m started up. thanks again.
sd_shadow said:
I suspect the battery is low and to 90% reading you were seeing was incorrect.
the battery could have also failed.
I would try to charge, if it does not boot to charge mode, you may need a fastboot cable and/or a new battery.
as long as ap fastboot says low battery you can not flash.
What is a Fastboot Cable
Click to expand...
Click to collapse
battery worked after one day charging. but none of mfastboot or fastboot lines wont work.
I'm sorry of this is a noob question, but I found this: http: // www . filefactory . com/folder/c6cdedc45a775d27 <--- which contained a bunch of stock roms. (I'm a new user, so I can't post links; just remove the spaces)
I bricked my phone with an incompatible SuperSU (stuck on Moto boot screen), so I need to flash 6.0.1 for XT1644 (I think it's unlocked/USA variant but idk)
I tried one that I found called "XT1625-XT1644_ATHENE-RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml_2.zip" which said that it was 6.0.1, but when I tried to flash, it said:
Code:
C:\Users\Mateo\Downloads\Extracted ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.044s
Apparently, I'm flashing the wrong version of the firmware, but there's like 10 pages of downloads on the filefactory link, and it takes about an hour to download each... Can anyone help me out here?
Thanks!
That firmware should be okay, however that error is normal if you're attempting to flash a build older than the build you currently have/had. I'm guessing you had either MPJ24.139-64 or Nougat on your device before? Your updated bootloader and gpt blocks any downgrades (and thus reduces the chances of bricking your device).
You may be able to flash your older firmware (and downgrading in the process) if you do not flash gpt or bootloader, omit:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
The rest of your flashing commands should be the same. Of course, verify your bootloader is unlocked (which it should be if you were flashing SuperSU), else you won't be able to downgrade.
Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:
matetoes said:
Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:
Click to expand...
Click to collapse
Woo, good to hear you've got your device working I think with the OTA, you should be okay as the bootloader blocked earlier attempts to downgrade and your subsequent flashes won't have affected those partitions, so it's unlikely you'll brick your device!
I decided to return my Sprint variant. So i needed to s-on and lock the bootloader. Problem is, now I have a 1 sec bootloop. Here's what I did. No idea how to fix the problem now.
Here's what I did in order to get the phone back to 100% stock to return it.
Changed the CID (incorrectly) to spsc_001 instead of spcs_001 but iddn't notice that.
Managed to get s-on but couldn’t get bootloader locked again.
reinstalled twrp and SU
booted up
installed sunshine and successfully s-off'd & locked
rebooted to download mode
Did a s-on using fastboot oem writesecureflag 3
rebooted and got a 1 sec bootloop
booted back into download mode and tried to factory reset via fastboot but can’t write the partition
tried to flash twrp, but got a security warning BL-unlocked
Now I'm stuck in a super short .5 second bootloop and can’t access stock recovery.
I try to install the ruu.exe and I get a Customer ID error. I try to install RUU.zip and I get a load_file: could not allocate -2146013644 bytes (which I assume means the partition is full but I can't even erase the userdata.) I also get a Security checking failed GT_CONNECT_FAIL on the download mode screen. I'm totally clueless as to how to get out of this situation. Anyone been here before or knows how to deal with this?
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
honestly, I think you're screwed...I don't know how you'll be able to fix this w/o being able to boot up, can't unlock bootloader, can't use fastboot to flash anything, can't flash RUU...somehow u need to get your CID back to SPCS_001...u may just have to return it in that condition & act ignorant.
any ideas @dottat @Captain_Throwback
vijn said:
Now, my vars are:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT64xxxxx6
(bootloader) current-slot:
(bootloader) imei: 99xxxxx1
(bootloader) version-main: 2.42.651.63
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: spsc_001
all:
finished. total time: 0.009s
Click to expand...
Click to collapse
OMJ said:
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
Click to expand...
Click to collapse
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
vijn said:
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
Click to expand...
Click to collapse
Well did you attempt to see if HTC dev would give you an unlock token at least?
Sent from my SM-G955U using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
You might be able manually flash the ruu partitions one by one as well. Have you tried that?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-G955U using Tapatalk
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
Click to expand...
Click to collapse
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
dottat said:
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
vijn said:
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Click to expand...
Click to collapse
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
OMJ said:
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
Ok well, I tried these.
The sd card method failed due to the CID mismatch.
The stock boot.img from the firmware zip method gave the following:
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
The Firmware flash via fastboot, no ext sd card needed gave this:
sending 'zip' (66180 KB)...
OKAY [ 3.269s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 6.456s
I'm screwed aren't I?
dottat said:
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
vijn said:
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
Click to expand...
Click to collapse
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
dottat said:
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
Click to expand...
Click to collapse
Ok, will try that. You wouldn't happen to know where I can find the zip would you? I always used the exe cause that's what was on the htc site. Not sure where the actul RUU.zip file can be found. I assume I can use the one found here: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
And dottat, OMJ, thanks a lot for your help. It's people like you who make this community what it is.
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
vijn said:
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
Click to expand...
Click to collapse
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
OMJ said:
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
Click to expand...
Click to collapse
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
vijn said:
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
Click to expand...
Click to collapse
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
OMJ said:
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
Click to expand...
Click to collapse
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
vijn said:
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120734364
Saw your post while looking for an sim unlock for my Japanese HTC 10.
Couldn't resist reading more about your problem tho.
First idea but quite dangerous if done incorrectly..
Try and see if you can change the cid in the ruu.exe with a HEX editor?
If that doesn't work, next try and change the cid of the ruu. zip.
Might be a long shot, but if the files cid's aren't encrypted it might work!
I've been doing this crap for nearly a decade now and the only time I've ever had so much trouble was back with the Evo 3D before they had that bootloader update that would only let you half-unlock or whatever and you had to intentionally corrupt the bootloader to flash a lower version.
I've been through 6 damn versions of twrp on this device, will not accept pin on new versions so 3.1.1.0-plotter works but it doesn't flash anything error 255. I update and again, will not accept my pin, wrong password it says.
I have been rebooting for the past 2 hours with nothing to show for it but twrp and being able to actually boot the stock rom (this was a problem at first, would boot loop into recovery). Somewhere along the line I got 'bad key' ID and don't know how the hell I did that but I continue to get '(bootloader) Image not signed or corrupt' in cmd.
What the actual **** is up with this phone? And how can I just get a nice AOSP non-gapps rom?
I've used the toolkit to re-flash stock rom so that is where I sit. Please help.
negativzeroe said:
I've been doing this crap for nearly a decade now and the only time I've ever had so much trouble was back with the Evo 3D before they had that bootloader update that would only let you half-unlock or whatever and you had to intentionally corrupt the bootloader to flash a lower version.
I've been through 6 damn versions of twrp on this device, will not accept pin on new versions so 3.1.1.0-plotter works but it doesn't flash anything error 255. I update and again, will not accept my pin, wrong password it says.
I have been rebooting for the past 2 hours with nothing to show for it but twrp and being able to actually boot the stock rom (this was a problem at first, would boot loop into recovery). Somewhere along the line I got 'bad key' ID and don't know how the hell I did that but I continue to get '(bootloader) Image not signed or corrupt' in cmd.
What the actual **** is up with this phone? And how can I just get a nice AOSP non-gapps rom?
I've used the toolkit to re-flash stock rom so that is where I sit. Please help.
Click to expand...
Click to collapse
U hardbricked your phone
dhinesh_cool said:
U hardbricked your phone
Click to expand...
Click to collapse
How? I'm up and running stock rom, got TWRP, and have Magisk installed for root so I can use it for now.
negativzeroe said:
How? I'm up and running stock rom, got TWRP, and have Magisk installed for root so I can use it for now.
Click to expand...
Click to collapse
First of all don't use toolkits. Learn the manual way, it's much safer. I'm not really sure that I understand your post correctly. The official TWRP recovery (3.2.1.0) isn't able to decrypt your data partition, that's why it asks for a pin. Just skip the step, go to Wipe and reformat /data (it's the part where you have to confirm with "yes", not just swipe).
Be aware that all of of your data stored in internal storage will be wiped.
Also make sure to enable OEM unlocking in developer options before you start.
After that your data partition should be decrypted and you should be able to install a custom rom.
Warning:
Make a nandroid backup of all your partitions incl.EFS before and backup also persist.
If you want to return to stock there I a high risk to lose IMEI,VoLTE,4G or all of them if you don't have everything backed up.
Here's how to backup persist:
https://forum.xda-developers.com/g5-plus/how-to/dev-fixing-baseband-t3806064/page2
The needed commands are
Code:
adb shell
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
for backup and
Code:
adb shell
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
for restoring.
Sent from my Moto G5 Plus using XDA Labs
OK I know how to do it the manual way. I've been doing this since 2009. Not to appear like a douche but I'm not new to root/rom/etc. Just this phone. Granted I've been away for a bit due to a work-issued Verizon Pixel, but I've gone through this process on Nexus devices, LG, HTC, etc. I've done everything I know to do but it's not doing...
I used the toolkit because I was lazy and only for the unlock itself, which was successful.
The official TWRP recovery (3.2.1.0) isn't able to decrypt your data partition, that's why it asks for a pin. Just skip the step, go to Wipe and reformat /data (it's the part where you have to confirm with "yes", not just swipe).
Click to expand...
Click to collapse
Here is the problem. If I skip, I can't do **** to my partitions, wipe, install etc.
Make a nandroid backup of all your partitions incl.EFS before and backup also persist.
Click to expand...
Click to collapse
Another problem. I did this but during trying to wipe data and install rom, it nuked my backups. I didn't know this, and now persist is gone. I found the guide to restore so that isn't an issue. Personally I thought Volte always made my call quality suck anyway.
Also I currently cannot boot recovery.....
Code:
~fastboot flash recovery twrp-3.2.1-0-potter.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16290 KB)...
OKAY [ 0.369s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.315s]
finished. total time: 0.685s
~fastboot reboot recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
fastboot: usage: unknown reboot target recovery
EDIT also Idk if it's important but it says 'n/a' where 'bad key' used to be on the "we hate you for unlocking" boot screen.
EDIT 2 I can with adb reboot recovery from within the os, when trying to back up, unable to mount storage.
EDIT 3 downgraded back to 3.1.1.0 and I can back up. I'll work with this and see what I get.
EDIT 4, can flash minor zips to no effect (no-verify), can back up, can wipe data and system partitions. Cannot install a rom. Error 7. I've confirmed that this is a plotter rom.
EDIT 5. Okay I can install Resurrection Remix NOUGAT, but cannot install any OREO roms. For whatever the **** reason I have no idea.
negativzeroe said:
OK I know how to do it the manual way. I've been doing this since 2009. Not to appear like a douche but I'm not new to root/rom/etc. Just this phone. Granted I've been away for a bit due to a work-issued Verizon Pixel, but I've gone through this process on Nexus devices, LG, HTC, etc. I've done everything I know to do but it's not doing...
I used the toolkit because I was lazy and only for the unlock itself, which was successful.
Here is the problem. If I skip, I can't do **** to my partitions, wipe, install etc.
Another problem. I did this but during trying to wipe data and install rom, it nuked my backups. I didn't know this, and now persist is gone. I found the guide to restore so that isn't an issue. Personally I thought Volte always made my call quality suck anyway.
Also I currently cannot boot recovery.....
Code:
~fastboot flash recovery twrp-3.2.1-0-potter.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16290 KB)...
OKAY [ 0.369s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.315s]
finished. total time: 0.685s
~fastboot reboot recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
fastboot: usage: unknown reboot target recovery
EDIT also Idk if it's important but it says 'n/a' where 'bad key' used to be on the "we hate you for unlocking" boot screen.
EDIT 2 I can with adb reboot recovery from within the os, when trying to back up, unable to mount storage.
EDIT 3 downgraded back to 3.1.1.0 and I can back up. I'll work with this and see what I get.
EDIT 4, can flash minor zips to no effect (no-verify), can back up, can wipe data and system partitions. Cannot install a rom. Error 7. I've confirmed that this is a plotter rom.
EDIT 5. Okay I can install Resurrection Remix NOUGAT, but cannot install any OREO roms. For whatever the **** reason I have no idea.
Click to expand...
Click to collapse
u want latest twrp for flashing oreo
Right but newest twrp cannot modify partition because it cannot decrypt data. Password incorrect.
Edit, used this one and after several times manually wiping data and rebooting back to recovery it eventually works: https://forum.xda-developers.com/showpost.php?p=75306024&postcount=76