Related
hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo
Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery
i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.
problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
nice work... let them try to fix that shiz!
Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse
philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna
The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Hamal said:
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Click to expand...
Click to collapse
did you read this http://forum.xda-developers.com/showthread.php?t=1730463
Thanks for the quick response. Yes I did read the thread. It was one of the first things I tried. I lock/unlock the boot loader successfully. However when I start the phone in normal mode I get the same message, seems like nothing changed.
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Hamal said:
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Click to expand...
Click to collapse
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
razi914 said:
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did, tried several, can't remember which Android version was that finally worked, however upon flashing after I started in normal mode the same **** - encrypted again like nothing happened.
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
sui785 said:
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well I only tried stock Android since this is what I really wanted. But does it make sense to try CM if stock does not work. IS there a chance CM works. IF you say I should try than I should I guess. Never thought about it. Thanks for the advice.
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Hamal said:
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Click to expand...
Click to collapse
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Jaizero I just did what you suggested. Followed the link you provided and did everything according to he procedure. There were no errors. However when I restarted the phone with the last command line and it booted up in normal mode there was the same message.
The screen looks like the one on the link below (not actually my phones, have no other one to make a picture with).
http://bensullins.com/wp-content/uploads/2011/12/Nexus-S-Decrypt-On-Reboot-Android-4-600x800.png
Also I do not know if it is relevant or not but when it boots the initial screen with the Google logo in the very beginning there is a closed lock icon below the Google logo, probably because of the encryption ?
Thanks for the help in advance again guys/girls.
jaizero said:
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
Sorry saw your reply a bit too late. Yes these are the exact commands I used. Followed them exactly as stated every step worked out perfectly.
And no there is no encryption messaging while I am in the bootloader mode.
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Hamal said:
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Click to expand...
Click to collapse
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
Locking/Unlocking the bootloader does not work tried it a couple of times already. Will try the rest of what you suggested and let you know how it goes.
Thank you for the advice.
beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
I looked around the forums, could not find this Android 101 link tough. Any chance you might help me find it. I know I sound lazy but I really can't find the thread. Also I was thinking could an USB Jig solve this problem ?
If all else fails you could try this...
http://www.extremetech.com/computin...encryption-and-security-put-it-in-the-freezer
https://www1.informatik.uni-erlangen.de/frost
I don't see why fastboot erase userdata wouldn't work...
Sdobron said:
I don't see why fastboot erase userdata wouldn't work...
Click to expand...
Click to collapse
Well I did try it. What I did might be wrong, but here it is:
I followed the guide by jaizero for flashing via fastboot, but instead inserted " fastboot erase userdata" before the "fastboot flash userdata userdata.img" line. Than there was an error message on the phone, not on the pc command line screen, but it was so quick that I could not read it. However the process continued and was okay according to the command window and everyting went on as normal. Alas to no vail since the result was the same.
Any ideas ?
Ah I also noticed than in fastboot mode it said HW Version: 9. Any idea what it means ?
Thanks in advance for taking the time to bother with my bull
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy A20 crap.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. I also don't know if this will work on other variants, as I only have these for MetroPCS, and from my understanding this will NOT obviously work for Verizon, AT&T, and Cricket phones.
I want to thank @diversenerd, and @jhjhjhjhjhjh for their hard work tinkering with the phone as I tried to figure it all out from their notes and instructions. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this, as the information wasn't quite clear in some places and I got some bootloops.
Introduction/Preparation
First, go and prepare by READING EVERYTHING IN THIS FORUM. Very important. Don't even jump into this without reading this thread here all the way to the last page: https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857 (this is so you know start to finish what worked for some might not work for this variant).
Second, unlock the bootloader. The MetroPCS variant can be unlocked by Motorola; follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). I did it in Firefox this go round and it sent the codes immediately . When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
***NOTES SO YOU DON'T FREAK OUT***
1. Every time you power up the phone after you unlock the bootloader Moto will try and make you feel like crap with a bad key error in the middle of a nice message that your phone is not to be trusted. :laugh: This is normal. Give it a minute, you havent broke it.
2. There is no custom recovery/TWRP for this variant, so read carefully so you don't delete something you might not be able to flash back later.
3. OEM Unlocking toggle switch is interesting. On my first phone it was activated once the bootloader is unlocked and greyed out to where it couldn't be accessed anymore; On the significant other's phone it is still accessible and can be toggled even with the bootloader unlocked.
Files
There is confusion in some of the threads about leaving the Sim Card/SD Card in while flashing. Yes, pull it out and flash without it. Flashing with the sim card/SD card in can cause problems flashing. I did my first phone without it, but forgot to take it out with my second and had to start from scratch. Avoid that step.
1. Get Minimal ADB and Fastboot (it's easier to use than Android SDK and smaller).
2. Download the Motorola Drivers from their site (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (This is a good thing to have to know your hardware responsibly).
4. Stock Firmware. I used XT1955-5_OCEAN_RETUS_9.0_PPO29.114-63-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml which is the US Retail software instead of MetroPCS's firmware because of the issues I was having with it straight out the box. Both of my phones flashed fine with it and you can find it here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ I used the 2nd one with success - the first one doesn't play nice with Magisk.
5. MagiskManager-v7.3.2 apk.
6.The Boot .img separately extracted from the Firmware listed in Step 4.
7. Root Checker.apk
8. Patience (and a good movie keeping you going).
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card and SD card is REMOVED from the phone. Again, this is to prevent problems in the flashing.
3. Make sure your wifi is OFF. Every time you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and immediately pushes updates galore.
4. Make sure you save Magisk and the Boot .img to your phone directly. Using the Download folder is a great place and easily accessible in Magisk. You will not be able to add files once in fastboot).
5. Make sure your developer options are activated.
6. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
7. Make sure to check CPU-Z for your hardware specs and to make sure you're avoiding potential problems.
8. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device). Once you flash, you have to constantly check USB to Transfer because it will not do it.
9. Make sure you have the STOCK CABLE that comes with the phone. This model is funky about using other cables.
10. Make sure you set your display to time out to ten minutes. If the phone screen goes to sleep mode, it may interfere with flashing.
Rooting
Here is the fun part. Please keep in mind you may get a bootloop. I did on both phones on the first try with two different methods. I was on the infamous March 1 2019 security update and still got a bootloop from the patching. The second phone I just flashed ahead of time to the new firmware and still got a bootloop until I flashed again. Expect it.
1. Go into your developer options and DISABLE Automatic Updates. This is important for later on.
2. With the phone on, install Magisk. Make sure you use the version 7.3.2 or update to it since it's the latest version at the time of this guide.
3. Say yes when your phone asks whether or not you want to install things from unknown sources. It will grant access for this application only.
4. Open Magisk Manager and turn on your Wifi. If you don't Magisk will hang at checking updates. If necessary, force close Magisk and open it up again with Wifi on. It should bring you to One Green Check Mark that Magisk Manager is Up To Date, and One Red Mark above it that says Magisk isn't installed.
5. Click install on that tab ONLY (there is no need to click install by the Green Check Mark one). Magisk will then ask you "Do You Want To Install Magisk v19.3(193000) now? and click Install again.
6. Under Select Method, navigate to the folder on the phone where you saved your boot.img file (or whatever you named it). Once you select it you will be taken to a screen where the letters are funky looking but spell FLASHING at the top. Once it patches your file, it will tell you when it's done. Should it hang or you get errors, you WILL HAVE TO REFLASH THE FIRMWARE AND START OVER.
7. When the screen tells you it's all done, plug your phone up to the computer and drag the patched img file (it should by default say magisk_patched.img) and put it in the folder with Minimal ADB and Fastboot.
8. Turn the phone completely OFF.
9. Plug your phone via USB cable into the computer.
10. Press Volume Down and Power to boot into fastboot mode.
11. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory or it won't work.
12. Type "fastboot flash boot thenameofyourrecoveryfile.img" and hit enter.
If all goes well it should flash to "a" partition, and you should see in the command prompt "image signed with key bad key" before it says done. If it doesn't take do not re-flash as it will flash to "b" partition which will definitely bootloop and ensure you have to reflash the firmware.
13. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
14. Wait for the bad key/device cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
15. Open Magisk Manager. The icons should be in green, letting you know you have root. Follow @diversenerd advice and Click Tap To Start SafetyNet Check. Make sure your Wifi is on for that check. This apparently tests to see if it can deceive Google checks and possibly install OTA (can't say I did all that, not a update junkie).
16. Install Root Checker and confirm root.
17. Disable Updates. I know this is hard for some people, but you dont know if a forced OTA update will take root away, and leave us with no option to get it back or roll back to an earlier version of Pie.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. I have no idea why it doesn't work device to device, but it doesn't. And while I thank @jhjhjhjhjhjh for giving up his original files, it was incompatible with my phone (even though we are on the same variant) and bootlooped me.
2. You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. You will lose everything datawise flashing and playing with the boot.img. My phone reset itself tinkering with flashing, every time. Don't be alarmed if it takes you through a reset.
4. I wasn't able to confirm by going into updates (couldn't find the system settings) and verifying that nothing said anything about Device Integrity Compromised. I just assumed it.
5. Magisik is TEMPERAMENTAL. So if first you don't succeed, reflash the firmware and try again.
6. You cannot just go into the Stock Rom file and extract the boot.img file, put it in the Minimal ADB file folder and flash it if it bootloops. YOU MUST REFLASH ALL THE FIRMWARE OVER.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, here's what you're going to have to do. And don't worry - it won't relock the bootloader.
1. Make a duplicate folder of Minimal ADB & Fastboot that is clean (doesn't have any boot images or any added files in it).
2. Extract the firmware to the folder where Minimal ADB & Fastboot are at on your computer.
3. Turn the phone completely OFF and back ON if you haven't done so yet. Make sure there is no Sim Card of SD card in it.
4. Press Volume Down and Power to boot into fastboot mode.
5. Plug your phone via USB cable into the computer.
6. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure all your firmware files have been extracted in the Minimal ADB directory or it won't work.
7. Cut, Copy, and Paste in Fastboot All Together the following:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
8. When it is done it will stop on fastboot reboot. Hit enter and the phone will reboot.
9. Repeat all steps in the Pre-Rooting and Rooting section to obtain root.
Hope this helps my fellow MetroPCSers. I boot looped both of my phones this evening and brought them back with this method, and eventually achieved root on the 2nd tries, respectively. Old girl is working and I got Root Explorer and Titanium Backup going full stop. At least this root was easier than on my E4, lol.:laugh:
I will try and answer questions if I can or point you in the right direction.
I believe my boot img was flashed to "b" partition and everything is fine...
do you know a way to sim unlock it?
edwardxi said:
I believe my boot img was flashed to "b" partition and everything is fine...
do you know a way to sim unlock it?
Click to expand...
Click to collapse
Make sure it is okay, because when I flashed it the first time and it flashed to "a" and it bootlooped the Moto intro, I only flashed the boot image again and it flashed to "b" and hung at the "This Device Cannot Be Trusted/Bad Key" Screen.
I have no way to test sim unlock as MetroPCS locks their sims to the phone via IMEI and don't let you hotswap them, mostly to charge you 11 bucks reactivation fee. But in theory it should be sim unlocked by flashing to a different Carrier/Retail Rom, or at least that is how in the more budget line phones it worked.
Articul8Madness said:
Make sure it is okay, because when I flashed it the first time and it flashed to "a" and it bootlooped the Moto intro, I only flashed the boot image again and it flashed to "b" and hung at the "This Device Cannot Be Trusted/Bad Key" Screen.
I have no way to test sim unlock as MetroPCS locks their sims to the phone via IMEI and don't let you hotswap them, mostly to charge you 11 bucks reactivation fee. But in theory it should be sim unlocked by flashing to a different Carrier/Retail Rom, or at least that is how in the more budget line phones it worked.
Click to expand...
Click to collapse
I have been using it for couples of days, and definitely, everything is fine:laugh:
For metro, it's controlled by their Unlock app, you can't simply flash a different rom to unlock it... used to $10 on eBay, now $40... too expensive
edwardxi said:
I have been using it for couples of days, and definitely, everything is fine:laugh:
For metro, it's controlled by their Unlock app, you can't simply flash a different rom to unlock it... used to $10 on eBay, now $40... too expensive
Click to expand...
Click to collapse
Well, on My E4 I was able to unlock it by flashing Lineage Nougat. I could put any sim in it but Metro, because they lock by IMEI. Can't speak for this one, I just jumped back to Metro from Tmobile, who was HIDDEOUS.
Maybe you might get lucky and get some Moto support from Chimera. Then for 11 euro you could unlock it with their tool. But stay on their behinds and make sure its working first.
Articul8Madness said:
Well, on My E4 I was able to unlock it by flashing Lineage Nougat. I could put any sim in it but Metro, because they lock by IMEI. Can't speak for this one, I just jumped back to Metro from Tmobile, who was HIDDEOUS.
Maybe you might get lucky and get some Moto support from Chimera. Then for 11 euro you could unlock it with their tool. But stay on their behinds and make sure its working first.
Click to expand...
Click to collapse
yeah, can't agree more, they are terrible...
@Spaceminer. This is the post I'm talking about
If you want to get rid of the bad key message at boot, you can flash the logo.bin file from the link below with fastboot. Just place the downloaded logo.bin in the minimal adb and fastboot folder, open a cmd window and type fastboot flash logo logo.bin and press enter. Next boot you should have a plain white screen with a large black moto symbol instead.
https://forum.xda-developers.com/g7-power/themes/remove-bad-key-start-boot-t3947359
Going to root mumy G7 power from metroPCS. Can anyone confirm is there a way to SIM unlock after root?
aggresive said:
Going to root mumy G7 power from metroPCS. Can anyone confirm is there a way to SIM unlock after root?
Click to expand...
Click to collapse
There is no SIM unlock per se with MetroPCS. They tie their SIMS into the IMEI of the phone you're using. So you can't just take the sim out and put it in another phone easy peasy without going through them and paying them to do it.
However, if a custom rom comes out, which will happen once we get a TWRP, you'll be able to do that probably on Lineage. But until then, there will be no confirmation.
Beetle84 said:
If you want to get rid of the bad key message at boot, you can flash the logo.bin file from the link below with fastboot. Just place the downloaded logo.bin in the minimal adb and fastboot folder, open a cmd window and type fastboot flash logo logo.bin and press enter. Next boot you should have a plain white screen with a large black moto symbol instead.
https://forum.xda-developers.com/g7-power/themes/remove-bad-key-start-boot-t3947359
Click to expand...
Click to collapse
This is correct and I have contributed my custom made logo.bin image on said thread, even though you can still see bad key its cute, lol.
i got it all rooted but now it shows i have no imei and sim status not available any suggestions do i need to flash modem or radio
626jose said:
i got it all rooted but now it shows i have no imei and sim status not available any suggestions do i need to flash modem or radio
Click to expand...
Click to collapse
try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Thanks figured it out i used the 2nd download like the op said. I didnt check to see if it was the same version i was on so it bootlooped and i flashed the whole thing so i downloaded the original firmware reflashed it that didnt work so i let it update and it came back good as new. So for anyone else doing this make sure its the same version youre on i found it on a different site just google it
626jose said:
Thanks figured it out i used the 2nd download like the op said. I didnt check to see if it was the same version i was on so it bootlooped and i flashed the whole thing so i downloaded the original firmware reflashed it that didnt work so i let it update and it came back good as new. So for anyone else doing this make sure its the same version youre on i found it on a different site just google it
Click to expand...
Click to collapse
I used the RETUS version and didn't have that problem; are you sure you didn't accidentally click the wrong version and flashed that (like a CDMA version)? At any rate, glad you got it back. Interesting you updated....I NEVER EVER EVER EVER do that because updating can break root if the manufacturer patches it.
Also, make sure you are on the OS version March1st; I didn't update my phone and used that stock.
Articul8Madness said:
I used the RETUS version and didn't have that problem; are you sure you didn't accidentally click the wrong version and flashed that (like a CDMA version)? At any rate, glad you got it back. Interesting you updated....I NEVER EVER EVER EVER do that because updating can break root if the manufacturer patches it.
Also, make sure you are on the OS version March1st; I didn't update my phone and used that stock.
Click to expand...
Click to collapse
Yep made sure to follow everything word for word pretty sure thats why it bootloops the 1st time then after you flash the whole thing it works ive looked at them and the one that matches my firmware is the last 1 with the 2nd one i had 2 unlock apps one from metro and one from tmobile idk if thats your case or something didnt flash right or dirty flashed i was wondering also if that twrp river works has anyone tried it or is there twrp for this device and is there a way to rewrite the imei using adb or some other way
626jose said:
Yep made sure to follow everything word for word pretty sure thats why it bootloops the 1st time then after you flash the whole thing it works ive looked at them and the one that matches my firmware is the last 1 with the 2nd one i had 2 unlock apps one from metro and one from tmobile idk if thats your case or something didnt flash right or dirty flashed i was wondering also if that twrp river works has anyone tried it or is there twrp for this device and is there a way to rewrite the imei using adb or some other way
Click to expand...
Click to collapse
@Geofferey has created an unofficial TWRP here https://forum.xda-developers.com/g7-power/development/port-twrp-g7-power-t3963738
Warning: DO NOT USE RIVER twrp - Our device is Ocean and River will Bootloop and possibly brick it.
We can't rewrite the imei or any of that yet - we still are working on custom roms. I've been trying to make stock roms for our variant, but unlike the old Moto I had, the new android OS has new permissions and all that with Pie and it keeps messing up on the porting.
Well after installing adaway and it not working i tried uninstall phone froze so i turned it off by holding the power button now its stuck in a bootloop idk if it finally ran out of power everytime i shut it off it kept rebooting can i recover without reflashing everything or do i have to start from scratch tia for the help
626jose said:
Well after installing adaway and it not working i tried uninstall phone froze so i turned it off by holding the power button now its stuck in a bootloop idk if it finally ran out of power everytime i shut it off it kept rebooting can i recover without reflashing everything or do i have to start from scratch tia for the help
Click to expand...
Click to collapse
I've never had that problem before, so I'll give my suggestions.
1. Try a factory restore from the Fastboot Menu. That may set everything easy peasy BUT it will wipe the phone.
2. If #1 doesn't work, then see if you can just reflash the magisk patch. That may do it.
3. If #1 and #2 don't work, then yeah, back to the drawing board.
Adaway maybe messed with Magisk; did you set the proper permissions in Adaway to give it root access? Anybody else care to weight in?
I'm not able to upload Magisk or boot.img directly to moto g7 phone from computer through Windows. I can transfer both to SD card, but doesn't allow access directly to phone file directly. Yes, bootloader is unlocked.
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5