Related
Hi,
I have a HP Slate 7 2800. It is fine. I got it rooted.
The next step is getting a custom ROM on the machine.
I tried CWM but it has no bootloader for the device yet. How do I go about investigating that? How do I make one for the device?
Fastboot does not work either, so I cannot unlock it. I tried customising an update.zip from the HP site, but the bootloader requires the update.zip to be signed, and it will not proceed in installing it.
I was thinking of mounting the /boot under adb or writing to it with dd (boot.img) but I am not sure if that will break it.
How do I actually crack the bootloader ? Can I do some kind of debugging over usb prior to the kernel being loaded? How does that work?
How are bootloaders generally cracked?
Thanks for information
aindriu said:
Hi,
I have a HP Slate 7 2800. It is fine. I got it rooted.
The next step is getting a custom ROM on the machine.
I tried CWM but it has no bootloader for the device yet. How do I go about investigating that? How do I make one for the device?
Fastboot does not work either, so I cannot unlock it. I tried customising an update.zip from the HP site, but the bootloader requires the update.zip to be signed, and it will not proceed in installing it.
I was thinking of mounting the /boot under adb or writing to it with dd (boot.img) but I am not sure if that will break it.
How do I actually crack the bootloader ? Can I do some kind of debugging over usb prior to the kernel being loaded? How does that work?
How are bootloaders generally cracked?
Thanks for information
Click to expand...
Click to collapse
im looking around for that but still very dificult to find any kernel rom or recovery fot that,
my problem is related to small internal storage and inhability to install app on the external sd card. do you have any solution for this?
sdlink give me a message : incompatible
Hi All,
I have this phone here that is softbricked, so I'm looking for a stock rom (boot.img, containing kernel and ramdisk) for HTC Butterfly deluxe_u.
It has recovery TWRP 2.8<something> installed, but it is useless, because the underlying filesystems cannot be mounted due to (IMHO) an incompatible kernel / ramdisk that sits on the device now.
Symptoms:
When trying to manually mount a partition, like /data according to /etc/fstab, the command fails with "Invalid argument".
When trying to format the partition (e.g. mke2fs -j ext4 /dev/block/mmcblk0p34), the command fails with "Invalid block count".
To my understanding, this means that the current kernel doesn't know how to deal with the underlying filesystems / partitions in flash memory.
I do have a fair understanding of Linux and hardware, but I've always worked on PC's. I'm a complete noob to hacking Android, so forgive my ignorance.
If someone could provide me with a stock boot.img file, I'd be very happy. And learn a lot about the ways that make Android tick
Thanks in advance,
Ollie
Hi all, just curious. I've been looking around for this boot image for about 2 weeks now, but I haven't been lucky.
What would you do to find one?
Thanks for any hints.
Ollie
htc deluxe [url]http://4pda.ru/forum/index.php?showtopic=433096&st=840[/url].
hi friends, i am from venezuela and have the same problem wich my htc butterfly, i find the stock rom here bye a i hope that found your solutions,
Yankrisken said:
hi friends, i am from venezuela and have the same problem wich my htc butterfly, i find the stock rom here bye a i hope that found your solutions,
Click to expand...
Click to collapse
Thank you, Yankrisken.
I'm trying to understand this Russian language website. I haven't mastered Russian yet, so I have to rely on Chrome translate for now.
I'll let you know the outcome.
Regards,
Ollie
Ollie65 said:
Thank you, Yankrisken.
I'm trying to understand this Russian language website. I haven't mastered Russian yet, so I have to rely on Chrome translate for now.
I'll let you know the outcome.
Regards,
Ollie
Click to expand...
Click to collapse
Hello Yankrisken,
This seems to be a link to a full install and cannot be used.
Thank you for your effort, though.
Regards, Willem
Ollie65 said:
Hi All,
I have this phone here that is softbricked, so I'm looking for a stock rom (boot.img, containing kernel and ramdisk) for HTC Butterfly deluxe_u.
It has recovery TWRP 2.8<something> installed, but it is useless, because the underlying filesystems cannot be mounted due to (IMHO) an incompatible kernel / ramdisk that sits on the device now.
Symptoms:
When trying to manually mount a partition, like /data according to /etc/fstab, the command fails with "Invalid argument".
When trying to format the partition (e.g. mke2fs -j ext4 /dev/block/mmcblk0p34), the command fails with "Invalid block count".
To my understanding, this means that the current kernel doesn't know how to deal with the underlying filesystems / partitions in flash memory.
I do have a fair understanding of Linux and hardware, but I've always worked on PC's. I'm a complete noob to hacking Android, so forgive my ignorance.
If someone could provide me with a stock boot.img file, I'd be very happy. And learn a lot about the ways that make Android tick
Thanks in advance,
Ollie
Click to expand...
Click to collapse
Your phone is x920e, NOT x920d !
Recovery has its own kernel, so you probably installed wrong recovery (x920d, DNA or some other like one m7).
Install the x920e recovery from my ViperDNA post in the General section and try to install that ViperDna ROM for x920e or try to recover your device
bokithq said:
Your phone is x920e, NOT x920d !
Recovery has its own kernel, so you probably installed wrong recovery (x920d, DNA or some other like one m7).
Install the x920e recovery from my ViperDNA post in the General section and try to install that ViperDna ROM for x920e or try to recover your device
Click to expand...
Click to collapse
Thanks Bokithq,
I'm fiddling with it.
With modified TWRP 2.7 (as per your post), I can't get adb to connect to the phone. However, with TWRP 2.8 I can.
After uploading the ViperDNA zip file, I reloaded TWRP 2.7 and tried to install from there. Installation does seem to work, but when rebooting, I get back in TWRP.
To be continued
Regards,
Willem
Ollie65 said:
Thanks Bokithq,
I'm fiddling with it.
With modified TWRP 2.7 (as per your post), I can't get adb to connect to the phone. However, with TWRP 2.8 I can.
After uploading the ViperDNA zip file, I reloaded TWRP 2.7 and tried to install from there. Installation does seem to work, but when rebooting, I get back in TWRP.
To be continued
Regards,
Willem
Click to expand...
Click to collapse
Is your phone S-ON?
if it is, you have to follow the procedure for S-ON users in that post and install boot.img manually via fastboot after installing ViperDNA ROM, and you have to install the ROM with that TWRP 2.7 ( TWRP 2.8 for x920e has some bugs like after ROM install when reboot is initiated it sometimes turns screen off ,won't reboot, and adb doesn't respond so you have to wait till battery dies).
bokithq said:
Is your phone S-ON?
if it is, you have to follow the procedure for S-ON users in that post and install boot.img manually via fastboot after installing ViperDNA ROM, and you have to install the ROM with that TWRP 2.7 ( TWRP 2.8 for x920e has some bugs like after ROM install when reboot is initiated it sometimes turns screen off ,won't reboot, and adb doesn't respond so you have to wait till battery dies).
Click to expand...
Click to collapse
Thanks Botikhq,
I haven't been able to get it to work yet, still trying.
Phone has S-ON.
I think I'll close this topic and continue to work from your original post (http://forum.xda-developers.com/htc...rdna-4-1-0-htc-butterfly-x920e-t3007086/page3).
Regards,
Willem
This is mainly a temporary repost of @rakomancha's TWRP announcement in a new thread. He is the maintainer of this TWRP but has not signed into XDA for a while. There is an updated TWRP that I wanted to share. When he comes back and creates his own thread, I will replace this post with a link to his.
-------------------------------------------------------------------------------------------------------------------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 3S 10 Z500M
The next big step forward for Z500M development is here!
This is the first working custom TWRP recovery for the Asus ZenPad 3S 10 Z500M [P027], based from TWRP v3.2.1.
diplomatic and I had both been working on a port separately, and I offered to test his version. In a few hours we worked out a functional and install-friendly version.
Please NOTE that this is NOT an official TWRP. After this post, I'll be working on making the port official and update here.
ACKNOWLEDGEMENTS
This project, and my own motivation, would not have been possible without the incredible work and input of:
diplomatic, who has been instrumental in propelling Z500M development forward. He worked on the issue of perm root and discovered and revealed important intricacies of the Z500M restrictive bootloader. By the end of Dec 2017, he developed a method to unlock the Z500M bootloader based on his amazing work with the Z380M. With amartolos as his testing assistant, the Z500M bootloader unlocking tool was quickly developed and released Jan 5th 2018.
overkillZ, who in Sept 2017 introduced us all to rooting the Z500M
toineh, who did legwork of establishing temp root by manipulating system permissions & redirecting files through adb. Then he took the boot.img posted by LGiki, explained how to patch it through Magisk and posted the first patched boot image. He also served as a guiding voice on this front.
amartolos, who first attempted perm flashing the patched boot image of toineh's method and worked with diplomatic on the developments afterward, which led us to today. Also has served as a guiding voice.
LGiki, who was the first to post an extracted WW_27 boot image that got things rolling forward
DISCLAIMER
This image has only been successfully tested by me at this point.
Please exercise caution and care when attempting to flash anything to your device.
You are completely responsible for any possible issues or damages resultant from undertaking the following procedures.
That being said, this image and method should be safe.
REQUIREMENTS
ZenPad Z500M tablet, upgraded to Android N
Bootloader Unlocked, using Diplomatic's tool. Tablet should be showing Orange State during initial bootup.
Root with Magisk installed, Permanent Root preferable
BACK UP YOUR INTERNAL USER DATA, in case you need to factory reset
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
Knowledge of adb/fastboot and basic Linux shell
INSTRUCTIONS
Ensure REQUIREMENTS are all met
Ensure to RE-READ all instructions and understand them before starting
Reboot into fastboot mode
do fastboot boot twrp-3.2.1-0-z500m.img, TWRP should boot up in a few seconds. The theme should be blue.
In TWRP, go to BACKUP and back up Boot, Recovery, Data, System and SystemImage. Full backup took me about 10GB of space.
Copy the created TWRP Backup to your PC or an external location for safekeeping
Copy the TWRP twrp-3.2.1-0-z500m.img to tablet storage if not done already.
In TWRP, go to INSTALL, select Install Image and choose the twrp-3.2.1-0-z500m.img. Installation should only take a few seconds.
Unplug from USB and Reboot back into Recovery through the REBOOT menu
If installation went well, TWRP should boot up in a YELLOW theme. From my testing, I'm confident it is functionally the same.
RESOURCES
In this shared folder are
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
version 0.5 of Diplomatic's Unlock Tool
diplomatic's Z500M device source
hxxps://mega.nz/#F!SQlyDapC!XbbW0fftZWFfVx2lmL_JUQ [down, get the file below]
GOING FORWARD
I successfully tested replacement of Magisk with SuperSU. My steps taken were:
"Completely Uninstall" Magisk through the Magisk Manager
reboot directly into Recovery
INSTALL a previously downloaded official SuperSU zip file & REBOOT
I very much enjoyed this process of developing for uncharted regions of Android technologies and I owe all of that to the existence of this forum and the people in it. Next, I am reading up on porting a custom ROM, LineageOS looked very nice. I'll update here with significant progress until I get capability to start new forum threads. Thank you all and enjoy delicious functional TWRP custom recovery on your Z500M for the first time in history. Here's to looking forward to development exploding on this device.
-------------------------------------------------------------------------------------------------------------------------------------------------------
NEW DOWNLOAD
Updated February, 2018
Fixes the yellow color rendering in installed mode
twrp-3.2.1-0-z500m.zip
ADDITIONAL WARNING: At first boot of TWRP, it will ask you if you want to keep system read-only. Touch the Keep Read Only button at this screen and only mount system in read-only mode if you need (rarely needed). This is necessary because of dm-verity and is no different than most Android 6+ devices. Unless you have unlocked your bootloader and installed permanent root with dm-verity disabled, mounting the system partition in r/w mode will make changes to it and your tablet will instantly become unbootable.
This is great. Tempted to try this. thanks for the effort!
Thank you very much, I did this and also switched to SuperSU with no problems!
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
ratus69 said:
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
Click to expand...
Click to collapse
Well, recovery of course. ...because it's a custom recovery.
Hey guys I hope you can help me I had my Z500m partially rooted using the patched Magisk boot method and accidentally erased some stuff before I could permanently root it. Everything snowballed and all I have now is my firmware stored on pc I can get to fastboot mode but I have stock recovery still. can i flash my firmware through fastboot? I’ve been researching and it seems with Mediatek it’s different or at least not as simple. All searches keep coming up for Zenfone and I’m lost. Apologies if Im in wrong area.
diplomatic said:
Well, recovery of course. ...because it's a custom recovery.
Click to expand...
Click to collapse
Well I'm glad having nothing done until I get a reply from the Master himself
Thanks a lot diplomatic !
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
mirek54 said:
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
Click to expand...
Click to collapse
hold volume + and - together for 10s
There was a time that it was unthinkable development. I appreciate the time that cames after. Nice tutorial!
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Hi, soleera,
To install TWRP, you must have some way to flash it and a bootloader that's either unlocked or doesn't care about unofficial images. I'm not sure that's possible in Z500KL. Look into that first. The Z500KL is about as much a version of this tablet as a Lenovo Tab4 is a version of this tablet. They are completely different platforms, just with a similar model name.
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
soleera said:
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
Click to expand...
Click to collapse
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
diplomatic said:
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
Click to expand...
Click to collapse
Sounds good, I'll see what I can do when I get the time.
For some reason one of the official unlock tools for a different model worked on my tablet - I believe it was for the ZE552KL, although I could be wrong since I can't seem to install it any more ("the package conflicts with an existing package by the same name"). I'm definitely unlocked though since I can flash using fastboot without any errors...
Since we now have official unlock. Any chance at custom roms for this device? I would love to see it get some oreo love.
soleera said:
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Click to expand...
Click to collapse
Hello soleera
Have you succeeded to port twrp to Z500KL?
Do you know of any custom recovery for Z500KL?
Do you know how to root it?
Dr.Ghobar said:
Do you know how to root it?
Click to expand...
Click to collapse
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
diplomatic said:
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
Click to expand...
Click to collapse
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Dr.Ghobar said:
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Click to expand...
Click to collapse
Basically, just do the procedure in this post. It's not that complicated. Reading through that thread may also help. Oh, and you have to unlock your bootloader first with an Asus unlock tool, as soleera has mentioned. I think the tool for the Z500M may work. It's essentially the same app for every device.
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?
I know that I probably won't get any help since this is a budget phone from a random company, but has anyone figured out how to get Android 10 on the phone? If not, does anyone know how to install Magisk or root this phone? I've read threads on how to install it, but they don't list this phone as supported. TWRP doesn't support Hot Pepper Ghost so how can I install Magisk? Kingoroot doesn't let me root the phone, so what is another way?
Because this phone is based on MediaTek MTK6762 chipset watch this video:
jwoegerbauer said:
Because this phone is based on MediaTek MTK6762 chipset watch this video:
Click to expand...
Click to collapse
Sadly, Shuame is not working. The website is down and every time I try to install it using a download from another website it says that windows UAC won't allow me to.
To download RootGenius Shuame here you go:
Root Genius
Root Genius 3.1.7 (Android rooting software) for Windows ✔ free download with 3 mirrors. Safe, secure and tested for viruses and malware.
root-genius.en.lo4d.com
jwoegerbauer said:
To download RootGenius Shuame here you go:
Root Genius
Root Genius 3.1.7 (Android rooting software) for Windows ✔ free download with 3 mirrors. Safe, secure and tested for viruses and malware.
root-genius.en.lo4d.com
Click to expand...
Click to collapse
When I tried to root, it says "Such a tough phone! Root...failed" :/
Did you ever get a custom ROM working on this phone? The default Android ROM is pretty annoying (blocks push notifications).
luckydliu010 said:
Did you ever get a custom ROM working on this phone? The default Android ROM is pretty annoying (blocks push notifications).
Click to expand...
Click to collapse
Try Project Treble. That's what I learned today from Reddit, but there isn't a way to install it since there is no TWRP file thingy for this phone. Do you know if I could install it using ADB or?!??
[email protected] said:
Try Project Treble. That's what I learned today from Reddit, but there isn't a way to install it since there is no TWRP file thingy for this phone. Do you know if I could install it using ADB or?!??
Click to expand...
Click to collapse
Wait are you Nightcore? LOL that's my thread . I am going to **** around with a Moto E5 (similar CPU, but has lots more documentation) and see if I can figure a way to load via ADB.
luckydliu010 said:
Wait are you Nightcore? LOL that's my thread . I am going to **** around with a Moto E5 (similar CPU, but has lots more documentation) and see if I can figure a way to load via ADB.
Click to expand...
Click to collapse
HUH??! LMAO! Yea, thats me. I'm also trying to get project tremble to work on a ZTE Blade X1 5G, but no luck. Wanna chat on reddit?
[email protected] said:
HUH??! LMAO! Yea, thats me. I'm also trying to get project tremble to work on a ZTE Blade X1 5G, but no luck. Wanna chat on reddit?
Click to expand...
Click to collapse
Yeah man, let's chat.
[email protected] said:
I know that I probably won't get any help since this is a budget phone from a random company, but has anyone figured out how to get Android 10 on the phone? If not, does anyone know how to install Magisk or root this phone? I've read threads on how to install it, but they don't list this phone as supported. TWRP doesn't support Hot Pepper Ghost so how can I install Magisk? Kingoroot doesn't let me root the phone, so what is another way?
Click to expand...
Click to collapse
Did you figure out how to unlock the bootloader? It fails everytime I try.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
SR_72_Blackbird said:
Did you figure out how to unlock the bootloader? It fails everytime I try.
Click to expand...
Click to collapse
I unlocked mine as soon as it came in today..
adb reboot bootloader
fastboot devices
fastboot flashing unlock_critical
then, if that doesn't unlock it, then do the age old "fastboot oem unlock"
DrScrad said:
I unlocked mine as soon as it came in today..
adb reboot bootloader
fastboot devices
fastboot flashing unlock_critical
then, if that doesn't unlock it, then do the age old "fastboot oem unlock"
Click to expand...
Click to collapse
Do you know how to root after unlocking bootloader?
How can we pull the boot.img from the os?
There is no firmware available for download.
I managed to unlock the phone using MTK Client on Ubuntu and plan on rooting the phone and installing a GSI. However, I accidentally bootlooped the phone and I think it has to do with dm-verity. I managed to extract some of the important firmware like boot.img and system.img. However, I didn't patch the boot.img with Magisk before the bootloop happen. Would anyone who has a Hot Pepper Ghost (HPP GS1) be able to install Magisk Manager and patch the boot.img attached for me? It would be very appreciated as I think it would solve my bootloop.
googlephoneFKLenAsh said:
Do you know how to root after unlocking bootloader?
How can we pull the boot.img from the os?
There is no firmware available for download.
Click to expand...
Click to collapse
I was able to get the boot.img and system.img using MTK Client after unlocking the bootloader. The post above has the boot.img and I would greatly appreciate if you could help me out with my problem.
SR_72_Blackbird said:
I was able to get the boot.img and system.img using MTK Client after unlocking the bootloader. The post above has the boot.img and I would greatly appreciate if you could help me out with my problem.
Click to expand...
Click to collapse
Mind to share how you bootlooped, so that others can avoid it?
Patched with magisk 24312:
googlephoneFKLenAsh said:
Mind to share how you bootlooped, so that others can avoid it?
Patched with magisk 24312:
Click to expand...
Click to collapse
Unfortunately, the patched boot.img still didn't fix the bootloop.
Currently, I am attempting to build TWRP for the device to see if that can fix anything. I used the twrptgen command to make a device tree for the Ghost with the boot.img and am trying to build TWRP, but I am running into an error.
I have posted on this forum (page 240) if anyone could help with that.
In terms of bootlooping, the process of unlocking the bootloader with MTK Client as documented in the GitHub went fine. After booting, it did show a dm-verity error and orange state saying the bootloader had been unlocked, but all was still fine. Proceeding, I decided to try to flash a GSI and this is where I ran into problems. I attempted to flash the original system.img again, but that didn't work. Also for some reason it wouldn't boot into recovery, even though it should be tied into the boot.img not system.img because of the A/B partitioning. However, I still have access to BROM mode for MTK Client and fastboot mode. I think the bootloop has something to do with dm-verity and vbmeta.img, but I have tried a lot on those lines with no prevail.
I think there are two fixes to this problem. One being TWRP, if I can successfully build it, and the second flashing the entire stock firmware with a flash.bin file and starting over. I didn't realize until it was too late that I should have backed up everything into a flash.bin file using MTK Client, and instead only backed up specific partitions.
It would be awesome if you could help me and post a flash.bin file to this forum of the stock firmware for the Ghost. The instructions on how to do that are here, but in specific are as follows (on a Linux distribution, preferably Ubuntu):
Code:
sudo apt install python3 git libusb-1.0-0 python3-pip
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
python3 setup.py build
python3 setup.py install
sudo usermod -a -G plugdev $USER
sudo usermod -a -G dialout $USER
sudo cp Setup/Linux/*.rules /etc/udev/rules.d
sudo udevadm control -R
**Make sure to reboot now before proceeding**
**To put the Ghost into BROM mode (which is how you will read the partitions) make sure it is powered off. Then run this command:**
python3 mtk rf flash.bin
**Then, press and hold VOLUME UP, VOLUME DOWN, AND POWER, all at the same time, and at the same time, plug the phone into the computer with a USB cable.**
**The phone should start reading all the partitions and once it is done, it will have outputed a flash.bin file for the Ghost**
Any update on this project? I've had two of these phones for years, would love to be able to load a different OS onto one of them.
One of mine appears to have already been flashed with a basic android 9. It has strange problems, like not detecting the fingerprint reader and a few other things I can't think of offhand. Anyway, you can tell it isn't the same as the other one.
The normal one I bought new, the odd one came from ebay.
Anyway, just wanted to check on this topic. I don't use either of them at this point. I like messing with these types of things for fun.
I'm going to try and get a TWRP working on this Hot Pepper today, I'll let you guys know...