Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?
Related
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
I know its kinda late but
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
noah_bfn said:
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
Click to expand...
Click to collapse
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Your phone sounds like it is soft bricked.
emersonsamuel said:
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Click to expand...
Click to collapse
Your phone sounds as though it is soft bricked. It can be brought back to life.
Follow here to un-brick your device:
https://forum.xda-developers.com/android/general/ulefone-power-5-twrp-root-project-treble-t3943714
Loyal_Guardian said:
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
Click to expand...
Click to collapse
Just use the spflashtool. Try multiple times and try my updated guide. Make sure you installed the drivers properly AND USE A GOOD CABLE. I had some hard times flashing with spflashtool, but it was just the cable.
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
GiantMurloc said:
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
Click to expand...
Click to collapse
can you boot into fast boot mode
muneeb rizwan said:
can you boot into fast boot mode
Click to expand...
Click to collapse
nope, the screen stays black and it doesn't even vibrate anymore
GiantMurloc said:
nope, the screen stays black and it doesn't even vibrate anymore
Click to expand...
Click to collapse
does your computer detects it
muneeb rizwan said:
does your computer detects it
Click to expand...
Click to collapse
the device list in linux stays the same when i plug or unplug it, so I think its not detected by the pc
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
StaryMuz said:
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
Click to expand...
Click to collapse
so, I broke my system img today, the phone was in a bootloop and I downloaded the system img and boot img from c.mi.com, then I found out that there is actually a logo.img for the splashscreen and tried to create my own, I thought it would be alright if I flash it and I could get back to fastboot if its not working. well seems like that was wrong, now the phone is not booting anymore :'(
I there any way to the phone before it tried to start the logo.img?
On my old lenovo tablet there was a software called mtk tool that was able to flash the device before it starts anything
so I found out that I could try to boot my phone into the edl mode, so I can flash it with mi flash tool, but I would need to remove the phone cover for that, so it would be my last option, any other idea?
The question is whether the phone doesn't actually report anything when connected to a PC. In Windows detection is easy, how it is verifiable in Linux I have no idea. The phone can report to different kinds of drivers, including the COM port. EDL mode can be triggered by test points from the phone's motherboard, but sometimes also by button combinations. I don't know of a suitable button combination yet, but it is used from the off state of the phone when the phone is connected to a PC.
As for the tablet connection you mentioned, it was definitely an MTK CPU and it has different procedures to upload than Qualcomm. With us, you have to connect the phone first.
So I tried it on my windows and it also didn't show up in device manager. Anyway I will buy a phone repair kid and try to fix it in the EDL mode, thank you ^^