Related
Hey! I need all your help, please. Yesterday, I saw that Motorola reveled a tool to unlock the bootloader of our tablet (I know, late). I read all the information about the process, and I could do this on my mz607 wifi. I downloaded all that I need, drivers and android sdk. After that, I rebooted the xoom on bootloader using adb command but....I can't do anything on this!!
I looked for some information about this, and I found in all forums that I can unlock bootloader with "fastboot oem unlock" command. It's false, I cant do nothing!! I rebooted my tablet and now, always run on bootloader and not boot system.
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
I found a germany forum with the same problem (I think) but I don't understand how they solved this.This the link
After this, I looked for other solutions and I found a tool of Motorola, RSDLite. I downloaded the correct file for my model, and when it flashing (7 step for the tool) not flash the boot.img! It's flash correctly other file packages (recovery.img, fastboot, etc) but it can't flash boot.img
Now, when I do "vol up+vol down+power" and select "Normal Boot", It doesn't do anything, the system would be missing!
I think it's can be a soft brick....or no, I dont know. I'm very worried about this and I would appreciate all your help.
Thanks. I'm waiting your answer.
Anybody can help me????
Ok, Anybody wants to help me!
Bye.
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Joshbone said:
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
runandhide05 said:
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
Click to expand...
Click to collapse
So I have to find the same files for my MZ607? boot, recovery and system?
runandhide05 said:
You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Click to expand...
Click to collapse
Joshbone said:
So I have to find the same files for my MZ607? boot, recovery and system?
Click to expand...
Click to collapse
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Mjamocha said:
Click to expand...
Click to collapse
What??
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Anybody more??
Joshbone said:
Anybody more??
Click to expand...
Click to collapse
Runandhide told you everything you need to know. You need to find the right regioned fastboot file for your mz607 and flash it. And that ypur bootloader is not unlockable. Any tutorial you were reading to unlock it would have to have been for the original xoom, not xoom2.
HELP! Possible Brick on Xoom MZ607 WIFI
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
f5bud said:
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
Click to expand...
Click to collapse
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Like the genius I am I've bricked mine too. It's a UK MZ607 that's been updated to JB from the US MZ609. I managed to delete the stock browser whilst trying to install a CyanogenMOD browser (long story) so figured I'd just repeat the steps that I used to flash the US MZ609 firmware. What I'd forgotten is that the first stage is to flash the US MZ609 ICS ROM then do an update to JB meaning I was effectively trying to downgrade. Everything flashes successfully except the boot partition which gives an error that it doesn't exist. Any ideas out there? I tried what I believe to be the original Fastboot file but no luck
Joshbone said:
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Click to expand...
Click to collapse
Also tried this and it fails when flashing the boot partition. I just ordered a factory cable to see if it can bring it back to life...
Is this zip still available?
alecbond said:
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
Click to expand...
Click to collapse
anybody who still has the mz607 files for a restore? The possible stock files link doesn't work any more...
http://sbf.droid-developers.org/xoom2/list.php
Hi,
I have come here seeking help for repairing my Nexus 5 which is stuck in bootloop. The phone wasn't rooted with possibly no custom recovery and it's bootloader is locked. And I am not sure which firmware was on it. And I also don't know what was done to it for it to become "bricked" as it was given to me in that state.
I can access the Bootloader Mode (a.k.a. Fastboot) but when I try to enter the Recovery Menu it gives me an Android logo with the red triangle with "No Command." written underneath it. And since the bootloader is locked, I am unable to flash a Stock ROM on the phone.
I have somehow managed to "temporarily" unlock the bootloader by entering the following command.
Code:
fastboot oem unlock
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
So I tried entering that command then I immediately entered the following commands to flash the stock 6.0.1 recovery.img
Code:
fastboot erase flash
fastboot flash recovery recovery.img
But in vain, as it still gives me the "No Command." Android logo when I run the Recovery Mode. I have also tried the same procedure with the TWRP recovery.img but with the same results.
I have also tried launching the flash-all.bat from the stock 6.0.1 right after running the bootloader unlock command mentionned previously. But it fails as i guess the flash-all.bat is programmed to reboot the bootloader before flashing. Thus re-locking the bootloader right before attempting to flash it.
I have come here seeking for help as I believe XDA is the most active Android community online.
If my post is somehow against any forum rules here, please be indulgent as this is my first time posting on XDA.
Thanks in advance.
At first, fastboot erase flash is not a working fastboot command. It is used to erase a partition: boot, cache, data...
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
NexusUser5 said:
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
Click to expand...
Click to collapse
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Primokorn said:
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
Click to expand...
Click to collapse
Yes the bootloader gets re-locked. And pressing Volume Up doesn't work either.
JonesL said:
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Click to expand...
Click to collapse
I've tried the tool and I can't get it to work properly as it gives me an error saying "partition.txt does not exist. Please extract the file from the total binary image."
UPDATE: I just got it to work. The SDRAM test passed but EMMC test failed. So that means it's hard-bricked right? And is changing the motherboard the only way to fix it?
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
audit13 said:
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
Click to expand...
Click to collapse
I suspect a hard-brick, so I am strongly considering it. Would you know if motherboards are carrier specific? Meaning if I get a motherboard from another carrier's Nexus, would it end up changing the carrier of my phone?
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
audit13 said:
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
Click to expand...
Click to collapse
Thanks a lot for your help, very much appreciated.
Hey folks sorry for my poor english
Well I woke up yesterday morning and my MotoG2013 went crazy asking for "backup account", and when I clicked on the notification asking for it, that simply crashed. Everything crashed, even android.phone and system processes. I rebooted the device hoping it was just some "normal" bug, since I rooted it never stopped bugging. But it simply reboots->keeps crashing->black screen.
Unfortunately it wasn't in debug mode when it died so I can't even use logcat. Anyway if I go bootloader->recovery it says /cache/* partitions are unreadable (???). Despite it all I tried with format, wipes, factory resets but nothing changes. Recovery is way buggy but it's impossibile to flash a new one. I tried TWRP, new Clockwork versions, Stock Recovery, nada de nada nothing. "Mismatched partition size" and old CWM still there, without even working. I can't reboot recovery, bootloader or even power my phone on.
At this point I was enough pissed off and tried desperate stuff like flashing stock rom, using "erase" commands from fastboot (well, I think my IMEI is gone.......) but none of this worked. MotoBoot simply WON'T flash. I tried fastboot, mfastboot, rsd lite, everything. I thought EMMC might be dead too....I don't know anymore
Sorry for long post and poor english, but does anybody have a hint about what the heck is going on with my phone? Every help would be appreciated
Bye
*Edit: I forgot that when I try flashing, the error is "Preflash validation fail"
Help pls
cyberpunkers92 said:
Help pls
Click to expand...
Click to collapse
what does bootloader say?
fastboot version and other details?
sd_shadow said:
what does bootloader say?
fastboot version and other details?
Click to expand...
Click to collapse
It doesn't help me much. Says my phone is unlocked (code 3)
Fastboot version 41.18, eMMC model, CPU and Ram models, transfer mode: USB connected. Also, my computer can recognize phone when I'm on bootloader but not in "normal" poweroff, because I disabled debugging a few days ago.
Bootloader just reports errors when I try flashing recovery (mismatched partition size), motoboot (preflash validation fail), gpt (it reports "downgrade" even though I had 4.4 and I tried to flash 5.1) and other random errors.
fastboot getvar info in spoiler
INFOversion: 0.5
INFOversion-bootloader: 4118
INFOproduct: falcon
INFOsecure: yes
INFOhwrev: 0x83C0
INFOradio: 0x1
INFOemmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
INFOram: 1024MB Hynix S4 SDRAM DIE=4Gb
INFOcpu: MSM8226 CS
INFOserialno: TA9290CNH4
INFOcid: 0x0007
INFOchannelid: 0x00
INFOuid: 0DEBC7020F000000000000000000
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmot_sst: 3
INFOmax-download-size: 536870912
INFOreason: Volume down key pressed
INFOimei:
INFOmeid:
INFOdate:
INFOsku:
INFOiccid:
INFOcust_md5:
INFOmax-sparse-size: 268435456
INFOcurrent-time: "Sun Aug 7 22:39:26 UTC 2016"
INFOro.build.fingerprint[0]: motorola/falcon_vfgbsl/falcon_umts
INFOro.build.fingerprint[1]: :5.0.2/LXB22.46-28.1/1:user/releas
INFOro.build.fingerprint[2]: e-keys
INFOro.build.version.full[0]: Blur_Version.220.27.1.falcon_umts
INFOro.build.version.full[1]: .VodafoneSL.en.GB
INFOro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
INFOro.build.version.qcom[1]: .04.04.02.048.045
INFOversion-baseband: MSM8626BP_1032.3105.93.00R VFGB_CUST
INFOkernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
INFOkernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
INFOkernel.version[2]: MP PREEMPT Thu Jan 22 16:15:51 CST 2015
INFOsdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
INFOsbl1.git: git=MBM-NG-V41.18-0-g5742832
INFOrpm.git: git=MBM-NG-V41.18-0-gcecd6e9
INFOtz.git: git=MBM-NG-V41.18-0-g99c1a7c
INFOaboot.git: git=MBM-NG-V41.18-0-g99084d5
INFOqe: qe 1/1
INFOro.carrier: unknown
all: listed above
finished. total time: 0.078s
Recovery doesn't work anymore, it doesn't even reboot itself or reboot in bootloader mode. I can access Recovery only from bootloader->Recovery or fastboot reboot-recovery
Unmountable partitions are /cache and /persist. Sdext is not recognized
A random CWM error
"E: can't open /cache/recovery/last_install
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed. Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache (File Exists)
W: can't unlink /cache/recovery/command"
Then, trying with wipe/factory reset
"E: unknown volume for path [/sd-ext]"
What the.....??? Why? Root issues? Flash memory gone? I seriously have no clue.....
cyberpunkers92 said:
It doesn't help me much. Says my phone is unlocked (code 3)
Fastboot version 41.18, eMMC model, CPU and Ram models, transfer mode: USB connected. Also, my computer can recognize phone when I'm on bootloader but not in "normal" poweroff, because I disabled debugging a few days ago.
Bootloader just reports errors when I try flashing recovery (mismatched partition size), motoboot (preflash validation fail), gpt (it reports "downgrade" even though I had 4.4 and I tried to flash 5.1) and other random errors.
fastboot getvar info in spoiler
INFOversion: 0.5
INFOversion-bootloader: 4118
INFOproduct: falcon
INFOsecure: yes
INFOhwrev: 0x83C0
INFOradio: 0x1
INFOemmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
INFOram: 1024MB Hynix S4 SDRAM DIE=4Gb
INFOcpu: MSM8226 CS
INFOserialno: TA9290CNH4
INFOcid: 0x0007
INFOchannelid: 0x00
INFOuid: 0DEBC7020F000000000000000000
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmot_sst: 3
INFOmax-download-size: 536870912
INFOreason: Volume down key pressed
INFOimei:
INFOmeid:
INFOdate:
INFOsku:
INFOiccid:
INFOcust_md5:
INFOmax-sparse-size: 268435456
INFOcurrent-time: "Sun Aug 7 22:39:26 UTC 2016"
INFOro.build.fingerprint[0]: motorola/falcon_vfgbsl/falcon_umts
INFOro.build.fingerprint[1]: :5.0.2/LXB22.46-28.1/1:user/releas
INFOro.build.fingerprint[2]: e-keys
INFOro.build.version.full[0]: Blur_Version.220.27.1.falcon_umts
INFOro.build.version.full[1]: .VodafoneSL.en.GB
INFOro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
INFOro.build.version.qcom[1]: .04.04.02.048.045
INFOversion-baseband: MSM8626BP_1032.3105.93.00R VFGB_CUST
INFOkernel.version[0]: Linux version 3.4.42-gdd242b0 ([email protected]
INFOkernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
INFOkernel.version[2]: MP PREEMPT Thu Jan 22 16:15:51 CST 2015
INFOsdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
INFOsbl1.git: git=MBM-NG-V41.18-0-g5742832
INFOrpm.git: git=MBM-NG-V41.18-0-gcecd6e9
INFOtz.git: git=MBM-NG-V41.18-0-g99c1a7c
INFOaboot.git: git=MBM-NG-V41.18-0-g99084d5
INFOqe: qe 1/1
INFOro.carrier: unknown
all: listed above
finished. total time: 0.078s
Recovery doesn't work anymore, it doesn't even reboot itself or reboot in bootloader mode. I can access Recovery only from bootloader->Recovery or fastboot reboot-recovery
Unmountable partitions are /cache and /persist. Sdext is not recognized
A random CWM error
"E: can't open /cache/recovery/last_install
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed. Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache (File Exists)
W: can't unlink /cache/recovery/command"
Then, trying with wipe/factory reset
"E: unknown volume for path [/sd-ext]"
What the.....??? Why? Root issues? Flash memory gone? I seriously have no clue.....
Click to expand...
Click to collapse
which model #?
which firmware versions are you using?
Can you flash TWRP? There are many twrp Versions to try
I got "mismatched part size" too, but twrp works perfect.
sd_shadow said:
which model #?
which firmware versions are you using?
Click to expand...
Click to collapse
Where can I see firmware version? I got no other access to phone info...only bootloader and fastboot getvar all...I don't
Model SM3767AE7B5 (or maybe 785, the label on the box is a little fuzzy)
Mattwmaster58 said:
Can you flash TWRP? There are many twrp Versions to try
I got "mismatched part size" too, but twrp works perfect.
Click to expand...
Click to collapse
I tried 5-6 TWRP versions and a few CWM too...nothing seems to change....I even tried double flash (flash recovery *recovery*, reboot bootloader, flash again), tried to flash once and directly go to recovery but nothing, there is always the same CWM version, a little "shaky" on the screen...
Strange thing is that fastboot says "OKAY" when I write it... I thought maybe I did wrong erasing recovery from fastboot, but it said the same even before and it was a desperate try...I had tried to change recovery (because mine isn't great) time few months ago and even if my phone was ok I NEVER managed to change it.
There's a sum of weird things and the phone seems totally unresponsive.
Additional error: I tried back flashing stock firmware and got "hab check fail" message from fastboot. What's this?
Thanks a lot to everyone that's trying to help, I'm not english native and sometimes I can't explain clearly where the problem is...
http://pastebin.com/UG8YQXFA
Ok this is what I get trying to flash all
cyberpunkers92 said:
Where can I see firmware version? I got no other access to phone info...only bootloader and fastboot getvar all...I don't
Model SM3767AE7B5 (or maybe 785, the label on the box is a little fuzzy)
I tried 5-6 TWRP versions and a few CWM too...nothing seems to change....I even tried double flash (flash recovery *recovery*, reboot bootloader, flash again), tried to flash once and directly go to recovery but nothing, there is always the same CWM version, a little "shaky" on the screen...
Strange thing is that fastboot says "OKAY" when I write it... I thought maybe I did wrong erasing recovery from fastboot, but it said the same even before and it was a desperate try...I had tried to change recovery (because mine isn't great) time few months ago and even if my phone was ok I NEVER managed to change it.
There's a sum of weird things and the phone seems totally unresponsive.
Additional error: I tried back flashing stock firmware and got "hab check fail" message from fastboot. What's this?
Thanks a lot to everyone that's trying to help, I'm not english native and sometimes I can't explain clearly where the problem is...
Click to expand...
Click to collapse
model # should be on the back cover towards the bottom of the phone
what is the firmware file name you are trying to flash
Sent from my XT1254 using XDA Labs
sd_shadow said:
model # should be on the back cover towards the bottom of the phone
what is the firmware file name you are trying to flash
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
Oh you meant Falcon XT1032 maybe
I tried several firmware, GPE_XT1032_KOTH49, GPE_51_XT1032_M005, well at least 6 versions, but always stock firmware for XT1032
Have you got any clue about what's going on? I tried pretty everything and I'm desperate
You can try the oneclick TWRP/5.1 GPE installer which can be found here: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
Just boot into bootloader and run the batch files and hope that your Moto G gets revived.
I flashed it. Motoboot went right and when I rebooted my phone it seemed to work but.......same wallpaper than before and when I opened "Settings" everything started crashing like before.
So....after all erases formats and stuff + flashings, it didn't even lose custom wallpaper???? There's something wrong here how is this possible?
I was thinking about "forcing" hard brick and trying to revive, the phone is completely unresponsive whatever I do/flash, it keeps going with same old recovery and same old screen. It's the weirdest hardware/software I ever had, it really seems like the phone didn't give a damn about what I put into, it doesn't even brick or stuff
What I get trying to wipe from CWM (recovery I had, that stays there EVEN AFTER "fastboot erase recovery"). I really don't know what to do...
In advanced options
cyberpunkers92 said:
I flashed it. Motoboot went right and when I rebooted my phone it seemed to work but.......same wallpaper than before and when I opened "Settings" everything started crashing like before.
So....after all erases formats and stuff + flashings, it didn't even lose custom wallpaper???? There's something wrong here how is this possible?
I was thinking about "forcing" hard brick and trying to revive, the phone is completely unresponsive whatever I do/flash, it keeps going with same old recovery and same old screen. It's the weirdest hardware/software I ever had, it really seems like the phone didn't give a damn about what I put into, it doesn't even brick or stuff
What I get trying to wipe from CWM (recovery I had, that stays there EVEN AFTER "fastboot erase recovery"). I really don't know what to do...
In advanced options
Click to expand...
Click to collapse
did factory reset in twrp?
Sent from my XT1060 using XDA Labs
sd_shadow said:
did factory reset in twrp?
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
Sd_shadow...ok I'm not the finest english speaker but I said from beginning and in almost every post that I'm totally unable to change recovery. I flash it and it says OKAY but when I reboot I got CWM like before, I tried ERASE RECOVERY too and when I reboot in recovery there's CWM.......formatted cache, erased recovery, reflashed everything and, after more or less 10 different firmwares and recoveries flashed with fastboot and with mfastboot + no less than 100 wipes/erases/formats all I got is:
OLD recovery CWM
Classical motorola logo boot
Screen with my OLD wallpaper
****load of error messages like "Motorola Contextual Services stopped working"
After a variable time (from 1 to n error messages we could say) the screen goes blank and I got to reboot.
As I said before the phone seems completely unresponsive to every kind of try...maybe it's hardware failure.
http://forum.xda-developers.com/moto-g/help/bricked-moto-g-emmc-failure-t2815499 I found this thread googling desperately and unfortunately my phone's issues are exactly those (though I have XT1032)
EDIT: this is my phone's status. When it died I had this wallpaper and I was in "only priority" mode because I set that up before sleep. The processes that crash are pretty randomic but often phone system or googlesomething or motorola contextual services. In this case, "phone" and "system" keep crashing in loop and the screen doesn't even go blank. In my last try (after the solution proposed by Dnlz) it crashed more slowly so I was able to set back notifications but it's back AGAIN to the "last snapshot" before death.
Images below
cyberpunkers92 said:
Sd_shadow...ok I'm not the finest english speaker but I said from beginning and in almost every post that I'm totally unable to change recovery. I flash it and it says OKAY but when I reboot I got CWM like before, I tried ERASE RECOVERY too and when I reboot in recovery there's CWM.......formatted cache, erased recovery, reflashed everything and, after more or less 10 different firmwares and recoveries flashed with fastboot and with mfastboot + no less than 100 wipes/erases/formats all I got is:
OLD recovery CWM
Classical motorola logo boot
Screen with my OLD wallpaper
****load of error messages like "Motorola Contextual Services stopped working"
After a variable time (from 1 to n error messages we could say) the screen goes blank and I got to reboot.
As I said before the phone seems completely unresponsive to every kind of try...maybe it's hardware failure.
http://forum.xda-developers.com/moto-g/help/bricked-moto-g-emmc-failure-t2815499 I found this thread googling desperately and unfortunately my phone's issues are exactly those (though I have XT1032)
EDIT: this is my phone's status. When it died I had this wallpaper and I was in "only priority" mode because I set that up before sleep. The processes that crash are pretty randomic but often phone system or googlesomething or motorola contextual services. In this case, "phone" and "system" keep crashing in loop and the screen doesn't even go blank. In my last try (after the solution proposed by Dnlz) it crashed more slowly so I was able to set back notifications but it's back AGAIN to the "last snapshot" before death.
Images below
Click to expand...
Click to collapse
You can try to boot TWRP using fastboot boot, this won't flash the image.
Erasing every partition on your phone was not very smart. Stop making choices without doing research.
Use mfastboot only.
Flash the latest XT1032 5.1 Retail US firmware image - it doesn't matter what firmware you had originally.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide logs of flashing process. Rename sparsechunks correctly, do not blindly follow tutorial commands.
Thanks a lot for "fastboot boot" hint. Hadn't seen it listed in commands, I didn't think I could! Anyway TWRP is unable to access /cache partition too...and wipe went apparently well (no errors) but, in fact, it DIDN'T wipe again
lost101 said:
Erasing every partition on your phone was not very smart. Stop making choices without doing research.
Use mfastboot only.
Flash the latest XT1032 5.1 Retail US firmware image - it doesn't matter what firmware you had originally.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide logs of flashing process. Rename sparsechunks correctly, do not blindly follow tutorial commands.
Click to expand...
Click to collapse
Tried right now. This time I've been able to boot the phone but the wallpaper and old settings stayed there. I was also able (between an error and another) to "enable" usb debugging but with no response from pc, I mean, it simply allowed me to tick the box with no effect. Because of "Settings" working apparently properly, I tried to do factory reset from phone. It's a blank button, I click and click on "erase all" but it simply doesn't.
That's absolutely weird...it's not THAT broken to say "yeah ok faulty hardware" but even after every kind of wipe it doesn't wipe.
I was thinking...motog has one only internal storage and no sd slot. Is it possible that this is a snapshot of last working system (shadow copy? sort of cache? I don't know) but memory has failed? Some files are apparently staying on memory (pics etc), I see them from TWRP file manager, and this is absolutely impossible because I destroyed that partition at least 100 times.
@cyberpunkers92 - There is nothing unusual about anything you have described. I read threads about it multiple times a week. It's classic emmc corruption symptomatology. Now stop talking about how strange it all is and do what I tell you to do.
@lost101 as I said, I did it and it didn't work. Nothing in logfiles, everything okay but I reboot and that's the same. I wipe by recovery and it doesn't wipe. Did you tell me to do more than this?
cyberpunkers92 said:
@lost101 as I said, I did it and it didn't work. Nothing in logfiles, everything okay but I reboot and that's the same. I wipe by recovery and it doesn't wipe. Did you tell me to do more than this?
Click to expand...
Click to collapse
I asked to see a log of the mfastboot flashing process. I want you to clearly state what happens; saying "it doesn't work" is not helpful.
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
try another usb port and/or another cable.
Velunavian said:
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
Click to expand...
Click to collapse
I have had this happen before except it did not prevent adb/fastboot from working. I just had to switch slots with the fastboot cmd ( fastboot --set-active=b or a ) depending on which slot you are currently on. Then flash the factory img. Are you sure you have the correct drivers installed for adb/fastboot? Have you tried a different usb port / different pc / different cord?
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for your reaction!
I'm sure I have the right drivers, but I will trie more ports, cables and another pc and keep you updated!
First update
So I couldn't get my pc to recognise my phone.
I then used a MacBook so I could use the official USB-C cable. I downloaded the android SDK platform-tools and the factory image. I placed the files from the factory image into the platform-tools folder. Then I used the command './adb devices' and it showed my device! But when I tried the next command, it said "no devices found". Now, when I do the same thing, no device will show up, even in the beginning.
Velunavian said:
So I couldn't get my pc to recognise my phone.
I then used a MacBook so I could use the official USB-C cable. I downloaded the android SDK platform-tools and the factory image. I placed the files from the factory image into the platform-tools folder. Then I used the command './adb devices' and it showed my device! But when I tried the next command, it said "no devices found". Now, when I do the same thing, no device will show up, even in the beginning.
Click to expand...
Click to collapse
adb does not work in fastboot mode. use ./fastboot
If there's a USB 3.0 port in the Windows PC, using a USB 3.0 cable even in a supposedly USB 2.0 port can cause problems. (I've been there, to the point that tech support actually shopped me a replacement because they were sure it was a hardware problem with the phone.)
What I used to fix it, to make sure that whatever it is about USB 3.0 that's causing the problem isn't also showing up in a USB 2.0 port in the same computer, was using a Type A to microUSB cable (that's a type 2 cable - there's no question) and a microUSB-to-Type-C adapter.
Then I ran Deuces Recovery, and the phone worked (after about 5 minutes of watching that thin grey line moving on the initial white screen). Evidently the constant "flash/reboot/flash/reboot" cycle fixes something that Google overlooked. (You may find that the phone got messed up enough that you have to format user data to get it working. My first attempt - without formatting user data - didn't work. Formatting it did.)
Thank you for your replie
Rukbat said:
If there's a USB 3.0 port in the Windows PC, using a USB 3.0 cable even in a supposedly USB 2.0 port can cause problems. (I've been there, to the point that tech support actually shopped me a replacement because they were sure it was a hardware problem with the phone.)
What I used to fix it, to make sure that whatever it is about USB 3.0 that's causing the problem isn't also showing up in a USB 2.0 port in the same computer, was using a Type A to microUSB cable (that's a type 2 cable - there's no question) and a microUSB-to-Type-C adapter.
Then I ran Deuces Recovery, and the phone worked (after about 5 minutes of watching that thin grey line moving on the initial white screen). Evidently the constant "flash/reboot/flash/reboot" cycle fixes something that Google overlooked. (You may find that the phone got messed up enough that you have to format user data to get it working. My first attempt - without formatting user data - didn't work. Formatting it did.)
Click to expand...
Click to collapse
Yes, I had the same idea! I will trie it a few more times with my macbook and if it doesn't work I will buy the adapter.
I used an usb 3.0 A to C adapter and a usb 3.0 A to A cable to connect my Pixel to a usb 3.0 port on my pc. I think this should work, but somehow it didn't.
Thank you so much!
munchy_cool said:
adb does not work in fastboot mode. use ./fastboot
Click to expand...
Click to collapse
It worked! I got my device back to normal.
Velunavian said:
It worked! I got my device back to normal.
Click to expand...
Click to collapse
Enjoy.
cmlusco said:
I have had this happen before except it did not prevent adb/fastboot from working. I just had to switch slots with the fastboot cmd ( fastboot --set-active=b or a ) depending on which slot you are currently on. Then flash the factory img. Are you sure you have the correct drivers installed for adb/fastboot? Have you tried a different usb port / different pc / different cord?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Velunavian said:
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,i have same Pixel2 in this Load Error. PC doesn't recognize your device,You just put in annother usb until PC recognize the device,because it needs times to recognize the device.
but,my devices can't fastboot boot twrp.img
it say :
downloading'boot.img'...
OKAY[1.269s]
booting...
FAILED(remote:FAILED to load/authenticate boot image:Load Error)
when i flash factory ROM ,it say:
''archive does not contain 'boot.sig' ^^^^^^^^^
Erase successful,but notautomatically formatting.
Can't determine partition type.
FAILED[command write failed[no error]]
HOw to unbick this devices?
---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------
cmlusco said:
I have had this happen before except it did not prevent adb/fastboot from working. I just had to switch slots with the fastboot cmd ( fastboot --set-active=b or a ) depending on which slot you are currently on. Then flash the factory img. Are you sure you have the correct drivers installed for adb/fastboot? Have you tried a different usb port / different pc / different cord?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Velunavian said:
Hello,
I have a problem I'm not able to solve myself. If anyone is able to help me, please do. Thank you!
I recently unlocked my bootloader, installed TWRP and rooted my Pixel 2.
When I tried to restore a backup using TWRP, my Pixel 2 somehow bricked. Now it is stuck at the bootloader that displays the following information:
Bootloader: mw8998-002.0067.00
Baseband: g8998-00164-1710262031
Product Revision: walleye MP1
UFS: 64GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: SLOT Unbootable: Load Error
I can't go anywhere from the bootloader. When I select an option it will boot again, so I can't boot into recovery.
I tried flashing the latest factory image using the latest ADB and fastboot files, but it doesn't recognize my device.
It could be the boot-slot, but if the console on my PC doesn't recognize my device, how am I able to change the slot?
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,i have same Pixel2 in this Load Error. PC doesn't recognize your device,You just put in annother usb until PC recognize the device,because it needs times to recognize the device.
but,my devices can't fastboot boot twrp.img
it say :
downloading'boot.img'...
OKAY[1.269s]
booting...
FAILED(remote:FAILED to load/authenticate boot image:Load Error)
when i flash factory ROM ,it say:
''archive does not contain 'boot.sig' ^^^^^^^^^
Erase successful,but notautomatically formatting.
Can't determine partition type.
FAILED[command write failed[no error]]
How to unbick this devices?
I got a 6a today, with the intent of learning about rooting. I've never rooted before, but was pretty involved with iOS jailbreaking so kinda a similar vein.
I wanted to get to Android 13 to get a fresh start (as opposed to rooting on A12 and upgrading), so i downloaded the factory image. I used the flash-all.sh script, but it got stuck on "Rebooting into fastboot." It then booted into the "Your Device Is Corrupt" screen, and would get stuck on the Google logo when it was booting. I finally got the A13 factory image to boot, but the "Your Device Is Corrupt" screen still showed every time i boot *as long as the bootloader is unlocked*. When I lock the bootloader it seems to be fine. After talking to a couple friends that have been rooting for a while, they somewhat think that I've done something to the NAND and should send back the device for a replacement. I'm not sure what to do now. Any suggestions?
You're fine...all androids have a warning screen after being unlocked.
Zaxx32 said:
You're fine...all androids have a warning screen after being unlocked.
Click to expand...
Click to collapse
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked
CobreDev said:
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked
Click to expand...
Click to collapse
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.
Lughnasadh said:
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.
Click to expand...
Click to collapse
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?
CobreDev said:
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?
Click to expand...
Click to collapse
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.
Lughnasadh said:
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.
Click to expand...
Click to collapse
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
No problem and yep, that's correct. Just make sure you don't boot into the slot which still has A12 on it. Good luck!
CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.
Lughnasadh said:
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.
Click to expand...
Click to collapse
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!
CobreDev said:
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!
Click to expand...
Click to collapse
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!
dannyzamora said:
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!
Click to expand...
Click to collapse
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!
CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!
Click to expand...
Click to collapse
Try with the last update
CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
Click to expand...
Click to collapse
??? It came out earlier this week. https://developers.google.com/android/images#bluejay
Ah, must've missed that thanks
CobreDev said:
Ah, must've missed that thanks
Click to expand...
Click to collapse
Did you manage to solve it?
dannyzamora said:
Did you manage to solve it?
Click to expand...
Click to collapse
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now
CobreDev said:
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now
Click to expand...
Click to collapse
Good news! Congratulations
Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty
jackfrost909 said:
Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty
Click to expand...
Click to collapse
Unless there's an FBI agent out to get you, nobody will care. Most people won't even know what an unlocked bootloader is. If you're scared of hackers so much, reflash stock and relock