success! - Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev

11/10/19 @ 3:05..successfully obtained root access for my 1st device!!
Bold N1
Rooted with Magisk
Flashed stock boot.img
Fastboot flash boot (boot.img)
Fastboot flash recovery (recovery.img)
I'm finally a big kid!!

What usb driver did you use? I'm stuck on fastboot <waiting for device>

ycgr2002 said:
What usb driver did you use? I'm stuck on fastboot <waiting for device>
Click to expand...
Click to collapse
Did u allow usb debugging in developer options ?

greeneyez15o said:
Did u allow usb debugging in developer options ?
Click to expand...
Click to collapse
Yes and allow for OEM Unlock. It's a windows 10 driver issue. I couldn't figure it out.
Luckily I was able to run in on a Linux computer. Fastboot worked fine and was able to unlock the bootloader!

Sergeantslaughter said:
11/10/19 @ 3:05..successfully obtained root access for my 1st device!!
Bold N1
Rooted with Magisk
Flashed stock boot.img
Fastboot flash boot (boot.img)
Fastboot flash recovery (recovery.img)
I'm finally a big kid!!
Click to expand...
Click to collapse
How exactly did you root it? What were the steps if you don't mind sharing. I've only rooted one phone and I followed a step by step tutorial on YouTube.

The easiest way I've found is to download magisk manager and the stock boot img for your device.open magisk manager and click install-download zip only.. then move the zip file and your stock boot img to the root of internal storage. Eg/storage/emulated/0/. Go back to magisk manager and click install/select and patch file. Navigate to where you stored your stock boot img and select it. Magisk will automatically flash and repck img file and will save it in your downloads folder as magisk_patched.img. enable and debugging in Dev options and reboot to bootloader. /Adb reboot bootloader. Once your phone is in fastboot mode type /fastboot devices to be sure your computer can recognize your phone. Should come back as a serial number followed by the word fastboot. Then type
Fastboot flash boot magisk_patched.img
You should get a success prompt. If successful then reboot using
Fastboot reboot
Once your phone loads back up check magisk manager to verify that everything is installed, should be two green checks. Then use a root checker to verify root.....and that's it!

Also, you have to make sure your bootloader is unlocked in order to do this....its very easy for the bold n1 just enable oem unlock in Dev options and the reboot to bootloader and type fastboot flashing unlock. Select yes on the prompt on your phone and then continue your process.

ycgr2002 said:
What usb driver did you use? I'm stuck on fastboot <waiting for device>
Click to expand...
Click to collapse
mtk droid tools all in one installer worked for me

davids_laughter said:
How exactly did you root it? What were the steps if you don't mind sharing. I've only rooted one phone and I followed a step by step tutorial on YouTube.
Click to expand...
Click to collapse
Did I mention that I did this on my Chromebook....no windows at all lol

Related

[Q] Stuck on Cyanogenmod Simple Recovery

Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Perez92 said:
Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Click to expand...
Click to collapse
Follow this nkk71's Return to 100% Stock Guide!
majmoz said:
Follow this nkk71's Return to 100% Stock Guide!
Click to expand...
Click to collapse
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Perez92 said:
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Click to expand...
Click to collapse
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
majmoz said:
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
P.S. I am STUCK in Cyanogenmod Simple Recovery. I am not able to power down the device or get to any other screen.
Perez92 said:
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
Click to expand...
Click to collapse
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
So I was able to get my device past the first prompt. I now see the white bootloader screen and it does say "FASTBOOT USB". I downloaded the latest TWRP and placed it in the same folder as ADB and Fastboot. I did the second command to flash it, however I keep getting the error "error: cannot open 'TWRP.img'. Any idea as to what I could be doing wrong?
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
Got it to work. Used adb to get into fastboot. Then opened up the CM installer and let it redownload cyanogenmod onto my phone.
Thanks for the help!

Manual Update using ota ( 5.01)

This only works coming from KNX01R!
Edit, Camazza has found you can flash the stock 5.0.1 bootloader and sideload the update. See here http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
Download the update here http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
1. Root using tonu42's method here http://forum.xda-developers.com/g-watch-r/development/root-root-twrp-r-t2960511
2. After verifying you have root re install the stock recovery for 4.4w.2 from intersectRaven here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 (same command used during rooting).
3. Boot in the system and upload the update
adb push 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip /sdcard/update.zip
4. adb shell
5. cp /sdcard/update.zip /cache/update.zip
6. echo 'boot-recovery ' > /cache/recovery/command
7. echo '--update_package=/cache/update.zip' >> /cache/recovery/command
8. reboot recovery
9. Update installs
Thanks to tonu42 for root and intersectRaven for the stock boot.
Use at your own risk.
Does it remain rooted after the update ?
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
nxt said:
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
Click to expand...
Click to collapse
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
Yup, I knew that part so didn't ask. But I finally got it working (had issues flashing recovery, had to switch usb ports).
All is good now, thanks!
EDIT: Looks like SuperSU is still installed though (won't run)
Everything else seems stock, I even did oem lock/unlock a few times, recovery is stock
Between step 4 and 5 you need to type su
You'll lose root and I am working on a fix.
Sent from my A0001 using XDA Free mobile app
Why all this manipulations? Why not use ADB Sideload?
superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
I don't think LG cares as long as the lock icon is gone. I've already screwed up and sent them a G2 that was on older radios with TWRP installed, and they sent it back factory flashed to the latest firmware (ZVA at the time).
AntonChernov said:
Why all this manipulations? Why not use ADB Sideload?
Click to expand...
Click to collapse
I'd like to know as well, which method is better/safer, this or ADB sideload?
Adb does not work in Stock recovery that is why twrp is needed, . I am having the same issue with supersu crashing once booted. I have not had a chance to look at it yet. If you shell in and su before the phone boots su works fine though.
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Nice, good catch. I'll add that to the first post.
Camazza said:
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Click to expand...
Click to collapse
superdave said:
Nice, good catch. I'll add that to the first post.
Click to expand...
Click to collapse
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
kanzone said:
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
Click to expand...
Click to collapse
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
b0gd4n said:
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
Click to expand...
Click to collapse
adb version
make sure the adb version is > 1.0.32
kanzone said:
adb version
make sure the adb version is > 1.0.32
Click to expand...
Click to collapse
hey, nevermind, I did fastboot flash recovery, not adb boot recovery. I just did that, and I am now uploading the zip....exiting!
thanks!
So wait, the command to flash recovery is what exactly? I've seen 3 different commands on this very page. Also, we do it from the bootloader screen, right?
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Are you trying to restore the stock recovery? If so, you fastboot flash recovery recovery.img on the stock image.
cottageboy said:
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Click to expand...
Click to collapse
hi,
when I am trying to flash the recovery I get this error:
fastboot flash rcovery recoveryll.img
target reported max download size of 268435456 bytes
sending 'rcovery' (6634 KB)...
OKAY [ 0.312s]
writing 'rcovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.403s
adb version
Android Debug Bridge version 1.0.32
any idea?
do I need to flash the new boot.img before?

HTC One Mini 2 - Problem with root

Hi everyone
I stuck with root procedure (first link when you type "htc mini 2 root" in google)
I did unlock bootloader with htcdev, I am able to run adb and fastboot - meaning I can restart my phone into fastboot loader but I cannot run TWRP recovery, I dont know why. I downloaded few versions of this .img file, I run command fastboot boot recovery xxxx.img, with some files there is no reaction at all, with file recovery-twrp-2.8.5.0 phone is restarting but into normal function, there is no twrp screen. I have CWM-SuperSU-v1.30 on sd card in the phone
Does anyone have clue what can be wrong here?
Thank you
pudlll said:
Hi everyone
I stuck with root procedure (first link when you type "htc mini 2 root" in google)
I did unlock bootloader with htcdev, I am able to run adb and fastboot - meaning I can restart my phone into fastboot loader but I cannot run TWRP recovery, I dont know why. I downloaded few versions of this .img file, I run command fastboot boot recovery xxxx.img, with some files there is no reaction at all, with file recovery-twrp-2.8.5.0 phone is restarting but into normal function, there is no twrp screen. I have CWM-SuperSU-v1.30 on sd card in the phone
Does anyone have clue what can be wrong here?
Thank you
Click to expand...
Click to collapse
you using wrong command.
try:
fastboot flash recovery xxx.img
for root i recommend using TWRP and flash the SuperUser.
Make sure you using the correct recovery image...
All you need in here
kativiti said:
you using wrong command.
try:
fastboot flash recovery xxx.img
for root i recommend using TWRP and flash the SuperUser.
Make sure you using the correct recovery image...
All you need in here
Click to expand...
Click to collapse
It didnt worked, I download again twrp files and this time I guess I found newest version which worked with fastboot boot recovery.img
Thanx anyway

I have a soft rocked Red Magic 3

Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?
Link not open bro
The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?
I already share nubia red magic 3 twrp check my all post
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk
terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....
I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?
JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.

[REQUEST] TWRP needed for HTC Desire 12!!

is there any TWRP img supported for HTC Desire 12???? been searching it for few days now...
Shahxada said:
is there any TWRP img supported for HTC Desire 12???? been searching it for few days now...
Click to expand...
Click to collapse
Did you find any solution
mesutsenol said:
Did you find any solution
Click to expand...
Click to collapse
I don't need recovery for this phone but I dumped stock recovery which can be used to make own twrp recovery. You can read and do instructions from this site
HTML:
https://gist.github.com/rokibhasansagar/15c8e728d94a6bd35a687aac73ef79a5
.
If you want just only root (probably this method is only way to get root on this device) just:
1. UNLOCK BOOTLOADER! (developer options -> oem unlocking -> connect phone to pc in fastboot mode -> write in adb "fastboot oem unlock")
2. flash patched stock boot via fastboot (fastboot flash boot <path to magisk_patched.img>)
3. Install Magisk Manager
4. Done!
_____
If you want do something with this phone I recommend to use SP Flash Tool. You need to install unsigned MT67xx USB VCOM DRIVERS (preloader driver). You must have scatter files too with partition addresses and sizes in hex and you must download preloader. You can do it downloading ota update from htc via HTC_OTA_Downloader (model: htc_breeze_dugl CID: HTC__401 version: 1.90.401.1) and unpacking it. You can find there scatter file with partition addresses and preloader. If you want turn on preload mode just turn off and connect phone to pc.
Before doing something I truly recommend do backup/dump all partitions in SP Flash Tool.
krzysiek546 said:
I don't need recovery for this phone but I dumped stock recovery which can be used to make own twrp recovery. You can read and do instructions from this site
HTML:
https://gist.github.com/rokibhasansagar/15c8e728d94a6bd35a687aac73ef79a5
.
If you want just only root (probably this method is only way to get root on this device) just:
1. UNLOCK BOOTLOADER! (developer options -> oem unlocking -> connect phone to pc in fastboot mode -> write in adb "fastboot oem unlock")
2. flash patched stock boot via fastboot (fastboot flash boot <path to magisk_patched.img>)
3. Install Magisk Manager
4. Done!
_____
If you want do something with this phone I recommend to use SP Flash Tool. You need to install unsigned MT67xx USB VCOM DRIVERS (preloader driver). You must have scatter files too with partition addresses and sizes in hex and you must download preloader. You can do it downloading ota update from htc via HTC_OTA_Downloader (model: htc_breeze_dugl CID: HTC__401 version: 1.90.401.1) and unpacking it. You can find there scatter file with partition addresses and preloader. If you want turn on preload mode just turn off and connect phone to pc.
Before doing something I truly recommend do backup/dump all partitions in SP Flash Tool.
Click to expand...
Click to collapse
dude this really helped a lot! its a shame we cant even get full stock firmware for modding purpose, thanks!

Categories

Resources