Bootloop on Page after fastboot boot custom recovery.

[Renate]

Originally Posted by Anghirrim

Will it work with fastboot flash, or I'll have to go with edl...

Same difference. You can also "fastboot boot whatever".

[Anghirrim]

Originally Posted by Renate

Same difference. You can also "fastboot boot whatever".

Lol no, if I can avoid opening my Page again... I'll go with a real flash, at least a long press on power button does reboot it.

[Anghirrim]

Flashed with EDL... Bricked again.....The good thing is that now it gets opened much faster.

[Renate]

First of all, have you tried an EDL cable?
That works on my Poke5 but not my Poke3.
Both my Pokes (and my phone) have magnetic reed switches too.

Um, you didn't use Windows Notepad to edit any files, did you?
I use the independently produced Notepad++ which is not related.

[Anghirrim]

Originally Posted by Renate

First of all, have you tried an EDL cable?
That works on my Poke5 but not my Poke3.
Both my Pokes (and my phone) have magnetic reed switches too.

Um, you didn't use Windows Notepad to edit any files, did you?
I use the independently produced Notepad++ which is not related.

Nope, not tested yet for the EDL cable. I still need to get some quiet time (without kids around) to make one.

And yes, I did use Notepad++.

Stock recovery flashed back. All is fine now (until next attempt ).

[Anghirrim]

Ok, I'll now make four attempts to identify what's buggy.

Attempt 1 (just extract and repack, to see if the Page can boot a repacked recovery, even without changes): ==> Success, boots fine

C:\>imgutil stock_recovery.img /x /v prop.default
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 2: ==> Failure, white screen

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 3: Skipped

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0 | ro.debuggable=1
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 4: Skipped

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0 | ro.debuggable=1 | ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 4: Skipped

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.secure=0 | ro.debuggable=1 | ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 5: Skipped

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> To Be confirmed
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 6: ==> Success, boots fine and adb under recovery enabled and can take commands

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default

Attempt 7: ==> Failure, boots fine and adb under recovery enabled, but can't take commands due to SELINUX context issue

C:\>imgutil stock_recovery.img /x /v prop.default
- Edit default.prop with Notepad++ ==> ro.debuggable=1 | ro.adb.secure=0
C:\>imgutil stock_recovery.img /r /v prop.default

[Renate]

Your first attempt (which worked) should have reduced the size of the recovery image by a lot.

Give me a link please to your original recovery.img so that I can see what's going on.

Edit: Oh, if #6 works, you're on the trail.

[Anghirrim]

Originally Posted by Renate

Your first attempt (which worked) should have reduced the size of the recovery image by a lot.

Give me a link please to your original recovery.img so that I can see what's going on.

Yes, the first one reduced the recovery image size from 100,7Mo down to 46,6Mo.

Hey, at least just changing the "ro.adb.secure=0" seem to be enough to enable adb and get it working. I can now reboot to edl mode from both running Android and Recovery, which is nice

So the attempt 6 works fine.

Now, having MTP working could be nice too.

While for the stock recovery, here you go!
https://drive.google.com/file/d/1Goi...ew?usp=sharing

[Renate]

Try the custom recovery I sent you.
It only makes a white screen, but you should have ADB.
Just for fun:

# start ttyscreen
# start autoupdate

No, don't do any update or plug anything in.
I just want to see what works.

# reboot

[Anghirrim]

Originally Posted by Renate

Try the custom recovery I sent you.
It only makes a white screen, but you should have ADB.
Just for fun:

# start ttyscreen
# start autoupdate

No, don't do any update or plug anything in.
I just want to see what works.

# reboot

Hey, just tried, it boots into a white screen as you said, but adb does not find any device. I can't adb shell your two other commands.

I've seen that you've changed the prebuilt kernel as well as added your two services in ramdisk /system/bin (plus another thing).

[Renate]

What did the screen show? The recovery menu or white or what?

Please try again, same download URL, new image.

[Anghirrim]

Originally Posted by Renate

What did the screen show? The recovery menu or white or what?

Please try again, same download URL, new image.

White screen only.

I'll try a bit later thr new one.

[Anghirrim]

Still no luck.

Boots to white screen, then nothing.

And if I "adb shell" or "adb devices", the screen flashes once. Then nothing.

[Anghirrim]

I might give TWRP a try.... There are three Motorola phones (Defy, G9 Power and G30) using the same SoC officially supported by TWRP.

The G30 seems to be my best chance as it is compatible with the branch I am using for the Galaxy Tab S9 FE.

I will have a look and eventually adapt the device tree.

[Anghirrim]

Originally Posted by Renate

First of all, have you tried an EDL cable?
That works on my Poke5 but not my Poke3.

Hey, I have made some progress on the EDL cable DYI (see attachment).

So, what you meant with EDL cable, is this type of cable (for which we find a ton of tutorials on the net). A USB-A / USB-C cable, where Gnd and D+ are bridged during boot up? Then released?

I have tested both green and grey, they match the proper USB-A contact. And the grey is actually the same Ground than the metallic mesh shield we can see on the background (and also the main metallic casing that is plugged).

Thanks,