Develop Bugs

Getting Bootloader unlocked tomorrow - have some questions

1. Do I need to restore the phone to rooted Stock prior to having Alejandrissimo unlock my phone?
2. With the locked bootloader, CWM installs itself to /system. Do I still use the same recovery, or is there a different one I'll need to use? Or do you no longer need to use the recovery?
3. Does unlocking the bootloader wipe the phone, requiring I install a new kernel and ROM right after?
4. How do I reinstall the stock kernel if I need to take my phone in for service? (Yes, I know about voiding the warranty.)

netizenmt said:
1. Do I need to restore the phone to rooted Stock prior to having Alejandrissimo unlock my phone?
2. With the locked bootloader, CWM installs itself to /system. Do I still use the same recovery, or is there a different one I'll need to use? Or do you no longer need to use the recovery?
3. Does unlocking the bootloader wipe the phone, requiring I install a new kernel and ROM right after?
4. How do I reinstall the stock kernel if I need to take my phone in for service? (Yes, I know about voiding the warranty.)
Click to expand...
Click to collapse
1) nope
2) all the kernels have a built in recovery, so that one doesn't really matter
3) nope, with testpoint, it just unlocks the bootloader, nothing else changes
4) Wotanserver or flashtool. I've used both multiple times on an unlocked bootloader.
Sent from my R800x using Tapatalk

Oh the wait is killing me. I feel like a kid waiting for Christmas to start!

netizenmt said:
Oh the wait is killing me. I feel like a kid waiting for Christmas to start!
Click to expand...
Click to collapse
Yupp, I completely understand the feeling
I'm gonna respond to your PM here, because it's general knowledge that should be for everybody
What you're gonna want to do is the following
1) Download this: http://www.mediafire.com/?bp6tlnv9r750rxr It's chevyowner's port of CM9
2) He does have a kernel included in his zip, but for some reason, my phone decided that it didn't like it so instead I used this one: http://forum.xda-developers.com/showthread.php?t=1541482
2) If you want the gamepad buttons mapped correctly, follow these instructions: http://forum.xda-developers.com/showpost.php?p=23507172&postcount=552
3) After you install the rom, but are still in Recovery, download this fine: http://www.mediafire.com/?su27w59c2qd25t1
Connect your phone, make sure /system is mounted, and enter adb shell, "mv /system/build.prop /system/build.prop.bak" exit and then "adb push C:\path\to\build.prop (or in you're in linux /path/to/build.prop) /system/"
4) Reboot, and enjoy!
Pax

How do you get one of these things unlocked? I see no option to pay.
And how fast does Alejandrissimo work at unlocking bootloaders?

paxChristos said:
Yupp, I completely understand the feeling
I'm gonna respond to your PM here, because it's general knowledge that should be for everybody
What you're gonna want to do is the following
1) Download this: http://www.mediafire.com/?bp6tlnv9r750rxr It's chevyowner's port of CM9
2) He does have a kernel included in his zip, but for some reason, my phone decided that it didn't like it so instead I used this one: http://forum.xda-developers.com/showthread.php?t=1541482
2) If you want the gamepad buttons mapped correctly, follow these instructions: http://forum.xda-developers.com/showpost.php?p=23507172&postcount=552
3) After you install the rom, but are still in Recovery, download this fine: http://www.mediafire.com/?su27w59c2qd25t1
Connect your phone, make sure /system is mounted, and enter adb shell, "mv /system/build.prop /system/build.prop.bak" exit and then "adb push C:\path\to\build.prop (or in you're in linux /path/to/build.prop) /system/"
4) Reboot, and enjoy!
Pax
Click to expand...
Click to collapse
Thanks, Pax. I've downloaded those now.... just waiting on Alejandrissimo to get on.
Mephikun said:
How do you get one of these things unlocked? I see no option to pay.
And how fast does Alejandrissimo work at unlocking bootloaders?
Click to expand...
Click to collapse
You go to the website http://unlock-bootloader.com/ and click on Unlock. There is a form you fill out with your contact info. Alejandrissimo will reply with an email and instructions. Payment is made through PayPal. My understanding is it only takes about 15 minutes or less once you get connected.

Well, I am unlocked - yay - but I cannot get fastboot to install a kernel. It's not seeing my device, even though the PC sees it other wise. <sighs> It's making me crazy!

netizenmt said:
Well, I am unlocked - yay - but I cannot get fastboot to install a kernel. It's not seeing my device, even though the PC sees it other wise. <sighs> It's making me crazy!
Click to expand...
Click to collapse
which of the following are you doing?
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Do you have the fastboot drivers installed?
Pax
(hint: you wanna use the second one )

Starting over from scratch. I flashed the r800x ftf file so I'm starting fresh. Then I flashed the new kernel. When I powered up the phone, I see "SONY" instead of "Sony Ericsson" so I figure that's the new kernel. Then it goes blank and doesn't do anything else and I can't get into recovery. I'll keep working at it.
Oh yeah, almost forgot. Once I load that fastboot driver, when I connect the phone to my PC in normal mode it's prompting me for an Android driver and can't find one that matches.
Gee, this is fun ! Frustrating, but fun !
Yes, I see - it's the back button instead of the volume rocker now. That would explain my Recovery issue. On to the next step !!

netizenmt said:
Starting over from scratch. I flashed the r800x ftf file so I'm starting fresh. Then I flashed the new kernel. When I powered up the phone, I see "SONY" instead of "Sony Ericsson" so I figure that's the new kernel. Then it goes blank and doesn't do anything else and I can't get into recovery. I'll keep working at it.
Click to expand...
Click to collapse
(Yes, the new kernel is flashed.) Try spamming the back button/volume rocker when you first feel it vibrate turning on... sometimes my phone can be a little finicky, so I start spamming buttons right away (that should get you into recovery) and from there you can install Cm9

paxChristos said:
(Yes, the new kernel is flashed.) Try spamming the back button/volume rocker when you first feel it vibrate turning on... sometimes my phone can be a little finicky, so I start spamming buttons right away (that should get you into recovery) and from there you can install Cm9
Click to expand...
Click to collapse
Yeah, it was the Back button instead of the Volume Rocker that was getting me. I'm going to have to replace the build.prop from within CM9 though because once I put the fastboot driver in place, my PC now prompts me for an Android driver and doesn't like the ones that came with the phone.
Woot, CM9 booting! - Let's see how it goes. Back shortly!

Since you're using a pc, do this
1) adb pull /system/build.prop
2) download winmerge (http://winmerge.org/)
3) Open up both the downloaded build.prop and the pulled one in winmerge.
4) Use root explorer (or something similar) to add in the different lines
(Winmerge highlights where two files are different, making it extremely useful for this )
Pax

Can't do the adb pull now because of the PC wanting that Android driver

netizenmt said:
Can't do the adb pull now because of the PC wanting that Android driver
Click to expand...
Click to collapse
Goto the zergRush thread in my signature and use the drivers in that post, that should get adb working again.
Pax

paxChristos said:
Goto the zergRush thread in my signature and use the drivers in that post, that should get adb working again.
Pax
Click to expand...
Click to collapse
I don't see a link for drivers in particular. Is it part of the SDK maybe?
EDIT: NVM - I'm blind. I haven't been to bed since 6 PM Friday.
EDIT #2 - When I try to install that driver, it tells me there is nothing in that location for my hardware.
EDIT #3 - And now it's working just fine... I think my PC is as tired as I am about now, lol
THANKS FOR ALL YOUR HELP, PAX!!!

netizenmt said:
THANKS FOR ALL YOUR HELP, PAX!!!
Click to expand...
Click to collapse
No problem, its what I do
Welcome to freedom (and never having to worry about the next update breaking root )
Sent from my R800x using Tapatalk

Bricked Watch -- Help!!

I rooted the watch successfully and then attempted to revert to stock using the instructions here: http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
. Midway through the restore of the system.img, my computer crashed and now the watch is stuck at the Huwaei logo. I can no longer connect to the watch over adb - attemps to do so show that the watch is "offline." Is all hope lost or is there anything I can try?

No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Edit...if it shows connected but offline, just try unplugging it and plugging it back in again.
Sent from my Nexus 6 using Tapatalk

brizey said:
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.

davpel said:
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
Click to expand...
Click to collapse
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.

brizey said:
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
Click to expand...
Click to collapse
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!

If you can get into the bootloader, maybe try restoring these instead? http://forum.xda-developers.com/huawei-watch/general/huawei-watch-stock-rooted-images-t3224930

davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.

brizey said:
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
Click to expand...
Click to collapse
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?

davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.

davpel said:
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
Click to expand...
Click to collapse
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.

1/4 Life said:
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
Click to expand...
Click to collapse
Tried that. I get the double vibration, but no bootloader.

FWIW, I just looked at a few of the 5.1 OTAs for other watches. I think the OTAs will work even if rooted. I looked at skin1980's init autoroot script, and I don't think it really touches any of the base system files...it only adds in the binaries. The updater script does a hash on all of the files that it is going to patch, then patches them if the hashes are OK. Given that we are not really touching the system files by flashing a custom ROM, I think we can make the OTA zips work. The kernel will likely not flash, but we can always build a new one from source if needed.

brizey said:
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
Click to expand...
Click to collapse
And i dont know why. I dd them like i said and they are completely stock.

davpel said:
Tried that. I get the double vibration, but no bootloader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)

1/4 Life said:
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
Click to expand...
Click to collapse
Thanks, but tried the LG method as well (both the swipe and the tap) and had the same results -- or lack thereof.

Has anyone else tried restoring to stock with success from Skin's files?

myke66 said:
Has anyone else tried restoring to stock with success from Skin's files?
Click to expand...
Click to collapse
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.

Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!

Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
davpel said:
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Click to expand...
Click to collapse
Agree 100%. I am returning my first watch, and flashed it back to stock and relocked the bootloader with no issues using the revised instructions. Going to keep my new one stock I think...got to cut down on the toys (Nexus 6, Nexus 7, iPhone 5s, custom PC, G37, surveillance system, house LED lighting conversion, etc. etc. Momma ain't happy, and I really want to spend more time with the kiddos.)

Who the hell needs to ROOT a damn smart watch?! I could see when it was 2 years ago with the first Samsung smart watch to sideload Android apps but this.... This is just stupid. Congrats
Sent from my SM-N910T using Tapatalk

HTC One m8 doesn't boot

So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16

ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).

Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:

ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.

So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.

Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse

It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it

ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.

Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?

Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

It now says Relocked then underneath security warning. Is that good?

ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.

Will i have to re unlock the boot-loader for the RUU.exe to work?

ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.

Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one

ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.

Yeah it says updating 0 out of 7 sending ........................

ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.

This is what comes up

It send that 1 had been sent then it said error

How to access EDL mode on g7 play?

How do you access EDL mode on this device? Fastboot oem blankflash does not work. It only returns a denied message. If your wondering why I need access to this mode it's so I can fix my baseband. I read somewhere here on xda that doing so may help me get the original baseband back.

Also require access to EDL mode, but can't find a way.
I have the same question...
Deep flash cables don't seem to work, although I just learned that I need to check the "ports" section of Windows device manager and not simply expect it to pop up like a new device normally would.
My G7 Play isn't bricked.
Not rooted, and no TWRP installed either.
I need to figure out a way to make a full disk image without destroying the data already present.
The options theoretically possible seem to be:
1. Root via exploit - I'm currently exploring the viability of privilege escalation from Ubuntu installed in Termux
2. Unlock the bootloader without formatting anything - Guides do exist for other phones, but I only get one chance to get this avenue right.
3. Enter EDL mode and backup the entire disk using Qualcomm's own software. - The easiest way (on paper), but the method to put this phone in EDL mode continues to elude me.
I'm aware of the typical three ways to get a Qualcomm device in EDL mode without bricking it...
Deep flash cable - doesn't seem to work, but I'll try again with freshly aquired knowledge.
ADB/fastboot command - I've tried all of them native to my device, and a few that were added from guides about other devices
JTAG "pins" - much more like pads than pins...
Can't find diddly about 'em.
Don't know if they exist on a G7 Play, or which two to short to each other if they are even there.
Anyone have a potential solution that i may have overlooked?

Not sure if this is what you need or not but here's s link for a PDF file that's chock fill of nerd stuff (schematics/pinouts/etc) regarding the g7 play (-4 variant, I think)
The term JTAG hits like 13 times so it might hey you in the right direction at least.
[Google drive]/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view?usp=drivesdk
(I've been a member forever but this is my first post. Not sure if I can post links or not so just replace the above with drive.goog...etc...)
If you have any problems with the link PM me and we'll sort it out.
Good luck.

travis.mcgaw said:
Not sure if this is what you need or not but here's s link for a PDF file that's chock fill of nerd stuff (schematics/pinouts/etc) regarding the g7 play (-4 variant, I think)
The term JTAG hits like 13 times so it might hey you in the right direction at least.
[Google drive]/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view?usp=drivesdk
(I've been a member forever but this is my first post. Not sure if I can post links or not so just replace the above with drive.goog...etc...)
If you have any problems with the link PM me and we'll sort it out.
Good luck.
Click to expand...
Click to collapse
You need 10 posts to share links
Clickable link
https://drive.google.com/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view
Sent from my ali using XDA Labs

How to over think the simple things?
Thanks for the input gentlemen,
I'll hang on to the literature for future reference.
Turns out that I was wayyyyyyyy over thinking it.
Motorola's adb and fastboot commands (particularly on Qualcomm socs) is highly contextual.
When the documentation said 'adb reboot edl' that's what it meant.
Not from the booted os though.....
From recovery (SMH).
Simple as that for anyone else who's trying to take a full disk image without unlocking their bootloader
I think I'll still pursue a root exploit via termux though.
It could help a lot of folks out who don't have a solid root solution (Samsung users).
I'm too close to just forget about it anyway.
Seems to be working out like the old adb temp root, but with the possibility of automating the process into something less cumbersome.

Select slot_b from TWRP, then reboot into fastboot. You'll brick and go into EDL. I just did it last night on accident.

ok so i have the xt1952-t variant i have no stock recovery ive flashed in fastboot stock android 10 rom (XT1952-T_CHANNEL_RV_9.0_PCYS29.148-154-8_cid21_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml) everything flashed fine but it wont boot it says no baseband and ro.full build is blank. everytime it says unable to read non-hlos and kicks me back to fastboot. also bootloader is locked still i have my unique key but without being able to boot to os i cant toggle oem unlock..... this has been so frustrating. I believe i need to blank flash the device but cant get to edl.... can somebody tell my noob @$$ how to fix this thing? its my friends device i think he issued an erase all command. ive tried oem config fsg-id tmo and oem config carrier tmo both say ok but nothing fixes it.....please sos. Thanks in advance.
EDIT* Got it to boot to stock recovery after all thanks
---------- Post added at 09:36 AM ---------- Previous post was at 09:12 AM ----------
when you say "adb reboot edl" from recovery do you mean adb sideload? didnt work for me help please?

chrisdsj said:
ok so i have the xt1952-t variant i have no stock recovery ive flashed in fastboot stock android 10 rom (XT1952-T_CHANNEL_RV_9.0_PCYS29.148-154-8_cid21_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml) everything flashed fine but it wont boot it says no baseband and ro.full build is blank. everytime it says unable to read non-hlos and kicks me back to fastboot. also bootloader is locked still i have my unique key but without being able to boot to os i cant toggle oem unlock..... this has been so frustrating. I believe i need to blank flash the device but cant get to edl.... can somebody tell my noob @$$ how to fix this thing? its my friends device i think he issued an erase all command. ive tried oem config fsg-id tmo and oem config carrier tmo both say ok but nothing fixes it.....please sos. Thanks in advance.
EDIT* Got it to boot to stock recovery after all thanks
---------- Post added at 09:36 AM ---------- Previous post was at 09:12 AM ----------
when you say "adb reboot edl" from recovery do you mean adb sideload? didnt work for me help please?
Click to expand...
Click to collapse
How did you get??

dmferrer89 said:
How did you get??
Click to expand...
Click to collapse
I honestly dont remember bro. ive moved a few times and i dont have that phone anymore, i did successfully fix it though. im working on xt2131-1 now.

LeeSylva said:
How to over think the simple things?
Thanks for the input gentlemen,
I'll hang on to the literature for future reference.
Turns out that I was wayyyyyyyy over thinking it.
Motorola's adb and fastboot commands (particularly on Qualcomm socs) is highly contextual.
When the documentation said 'adb reboot edl' that's what it meant.
Not from the booted os though.....
From recovery (SMH).
Simple as that for anyone else who's trying to take a full disk image without unlocking their bootloader
I think I'll still pursue a root exploit via termux though.
It could help a lot of folks out who don't have a solid root solution (Samsung users).
I'm too close to just forget about it anyway.
Seems to be working out like the old adb temp root, but with the possibility of automating the process into something less cumbersome.
Click to expand...
Click to collapse
You can't reboot to EDL from recovery using the phones interface nor ADB if in sideload mode etc. This just isn't possible.
There are a lot of custom made ADB versions out there other than the stock platform tools. These other ones contain special commands for various brands that support them. I do know these will work but unfortunately only testpoints, bricking, or like smoeone said possibly changing configuration of boot are the only ways to get into EDL I can think of.

I never could get motorolas into EDL switching between slots and such with TWRP.
Spaceminer said:
Select slot_b from TWRP, then reboot into fastboot. You'll brick and go into EDL. I just did it last night on accident.
Click to expand...
Click to collapse
Seriously? That's odd. What build? I could never achieve this (didn't try intentionaly either) . Every time I would do as you explain for testing purposes my phone would simply reboot to TWRP or back to slot a. This is with majority of motorolas i have with slots and with no configuration changed by me.

fastboot oem blankflash

Just UNBRICKED Redmi Note8 PRO - This works need someone to test!!!

So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
Code:
fastboot devices
fastboot flash boot boot.img
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC

dcindallas said:
So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC
Click to expand...
Click to collapse
Thanks for sharing this. I've had a bricked rn8 pro for 3 weeks now and none of the other fixes worked for me. I'm looking forward to giving this a try when I get home from work. Perhaps I should've tried using my Kali box rather than windoze in my previous attempts.
I'll update with results if interested.

Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?

To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account

Yup on Arch Linux and this worked fine

Melon_Bread said:
Yup on Arch Linux and this worked fine
Click to expand...
Click to collapse
What you did? Pls help ):

GERATKDASD said:
What you did? Pls help ):
Click to expand...
Click to collapse
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)

Melon_Bread said:
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)
Click to expand...
Click to collapse
I will try, thanks

Still not working ): IDK if I don't doing it right, I don't know, I'm tired of this phone ):

GERATKDASD said:
Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?
Click to expand...
Click to collapse
I already tested battery draining, doesnt worked :/

KonahZave said:
I already tested battery draining, doesnt worked :/
Click to expand...
Click to collapse
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.

Sed lyf
GERATKDASD said:
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.
Click to expand...
Click to collapse
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)

KonahZave said:
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)
Click to expand...
Click to collapse
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.

pablo159 said:
To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account
Click to expand...
Click to collapse
None of that matters and no the preloader was over written, the point here is it was hard bricked only got the white LED light, then I did exactly what I wrote and it saw the phone in fastboot and it wrote the boot.img and then it rebooted and worked. Period. Worked for me. Someone else tested it worked for them. Try it but follow the directions....

dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Man, Im not trying this method or such thing, Im not bricked. Im just telling for the dude my old experience with old guides.

dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?

GERATKDASD said:
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?
Click to expand...
Click to collapse
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas

dcindallas said:
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas
Click to expand...
Click to collapse
Ok, so, you only need to installed adb and fastboot right? no drivers or other things?