Greetings,
Upon unboxing my OPO X and discovering it's limitations in regard to customization compared to Cyanogen (following this guide :
HTML:
http://oneplus.wonderhowto.com/how-to/install-cyanogen-os-12-your-oneplus-one-0161384/
),
I attempted to flash it using TRWP which I managed to install and start properly.
Either I messed something up with the install process or selected the wrong build for my specific phone (used YNG1TAS0YL-bacon-signed) but I was prompted to reboot my phone upon what I though was completion and ended up with no OS, hard bricked with QHSUSB BULK showing in device manager and totally blanked screen.
I then attempted to fix my own mess by following this guide :
HTML:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
which suggested I uninstall the faulty driver and replace it with the one suggested.
By doing so, I then ended up with an unknown device and from there my real nightmare started.
I've about tried every single restore guide I could find narrowing my search to my specific model this time figuring it would prevent compatibility issues but still nothing is working.
The sum up what is currently going on with my phone, if I press Power + Volume up, I get "Qualcomm HS-USB QDLoader 9008" listed under the "Ports" section of the device manager. However I now get a result with QCOMDownloadTool (which fail to to anything but is listed in some guides). No access to either fastboot or ADB.
On the other end, Power + Volume down booting will list whatever drivers I've choosen among Google, Samsung, Universal ADB or OnePlus i've tried to install and will list the device as an "Android device". This give me access to fastboot, however ADB never ever detect any devices and attempting to boot the "twrp-2.8.7.0-onyx_f2fs_r5.img" will display "FAILED (remote:dtb not found)".
Also, I noticed that within driver detail under "hardware id's" I get :
USB\VID_18D1&PID_D00D&REV_0100
USB\VID_18D1&PID_D00D
but with the official "OnePlus_android_winusb.inf" it is not replicated for adb value with instead
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D ;fastboot
%SingleBootLoaderInterface% = USB_Install, USB\VID_2A70&PID_D00D ;oem fastboot
%SingleAdbInterface% = USB_Install, USB\VID_2A70&PID_4EE7 ;adb
I'm all out of ideas, looking to try and fix it myself (with your help of course) before I go begging OnePlus customer support to save me.
Thanks in advance folks!
Try booting with your stock recovery. Img if you think it boots in fastboot
Sent from my ONE E1003 using Tapatalk
loveboy_lion said:
Try booting with your stock recovery. Img if you think it boots in fastboot
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I think the most basic problem is that no matter what driver I attempted to use so far, end up not showing in ADB.
I don't know the relation between ADB and fastboot, but I probably don't have a fully functional driver.
I made I backup with TWRP before wiping, but I don't think "recovery.emmc.win" & "recovery.emmc.win.md5" will help me a whole lot from fastboot.
Any idea where to get an image file of the stock recovery and the exact commands sequence to be used afterward?
It might sound like I have an idea of what i'm doing because I've been trying to fix this mess for 2 days, but I really don't...
KrapnoV said:
I think the most basic problem is that no matter what driver I attempted to use so far, end up not showing in ADB.
I don't know the relation between ADB and fastboot, but I probably don't have a fully functional driver.
I made I backup with TWRP before wiping, but I don't think "recovery.emmc.win" & "recovery.emmc.win.md5" will help me a whole lot from fastboot.
Any idea where to get an image file of the stock recovery and the exact commands sequence to be used afterward?
It might sound like I have an idea of what i'm doing because I've been trying to fix this mess for 2 days, but I really don't...
Click to expand...
Click to collapse
if i am understanding you correctly then you tried to install oneplus one twrp and rom on oneplus x if you really did so no wonder device is bricked since either you erased all your partitions (which is bad since oneplus did not release files required to debrick hardbrick device) if you only messed up your recovery then you would need stock recovery.img of your e1005 since recovery.img of e1003 most probably wont work you could try though
regarding if you are not sure if your phone is connecting in fastboot or adb try uninstalling all drivers you have installed and install the below drivers and hope your phone is in fastboot mode
https://drive.google.com/open?id=0B48lBYmwzkD5WlFrU2lNb2d5WlE
---------- Post added at 05:40 AM ---------- Previous post was at 05:33 AM ----------
if you have fastboot chances to repair your phone are 99%
your device wont detect under adb
---------- Post added at 06:01 AM ---------- Previous post was at 05:40 AM ----------
you could also check this for help
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Well, either I have rebooted before the installation was completed or I had the wrong kernel, but I no longer get any visual response from my phone beside vibrations when I power it on/off.
The drivers currently installed are the ones you provided, still there is nothing in ADB.
I can start a cmd fastboot and get a results from "fastboot devices".
See screen capture blow:
i.imgur(dot)com/KnFmTcf.jpg
i.imgur.(dot)com/4kat7Cv.jpg
I doesn't go any further than that, phone is still dead.
its good news for you
you are in fastboot mode
instead of installing twrp recovery install your stock recovery
it wont flash twrp since its getting dtb error and fastboot wont allow it to load since this version of twrp is for e1003 and yours is e1005
Where can I get an .img of the stock recovery?
I already did overwrite with TWRP so stock recovery is no longer present on the phone right?
I saw this file but I don't think I can use it:
drive.google(dot)com/file/d/0B0pr-ZA5b-1pM1prTmMwQmhOMXM/view?pli=1
you could try it hope it works chances of it working is 50%
fastboot flash recovery recovery.img
fastboot boot recovery.img (if this does not work and manualy try with power+volumedown)
---------- Post added at 06:40 AM ---------- Previous post was at 06:34 AM ----------
you are not alone with same problem
http://forum.xda-developers.com/oneplus-x/help/users-twrp-t3258756/post64071152#post64071152
---------- Post added at 06:49 AM ---------- Previous post was at 06:40 AM ----------
unless someone makes unified build of twrp for e1003 and e1005 you will face same problem if u try to flash twrp again
I do NOT have access to a "recovery.img" file on my phone.
What can I do next? Can these files I made a backup from be of any help currently?
i.imgur(dot)com/uEPBECy.jpg
yes the files are of help but only when u have twrp they cannot be used by fastboot
---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------
try flashing this twrp recovery
http://ns336247.ip-91-121-110.eu/h2o64/onyx/twrp/
Bacon is for the oneplus one...
KrapnoV said:
Well, either I have rebooted before the installation was completed or I had the wrong kernel, but I no longer get any visual response from my phone beside vibrations when I power it on/off.
The drivers currently installed are the ones you provided, still there is nothing in ADB.
I can start a cmd fastboot and get a results from "fastboot devices".
See screen capture blow:
i.imgur(dot)com/KnFmTcf.jpg
i.imgur.(dot)com/4kat7Cv.jpg
I doesn't go any further than that, phone is still dead.
Click to expand...
Click to collapse
Do you realize you tried to install stuff for an entirely different phone? OnePlus One is not OnePlus X. There was the problem with your installs...
If you get into to fastboot I would try flashing something that is made for OnePlus X and see how it goes.
I would be very happy to flash a compatible rom this time, but while fastboot SEEM to work, i'm not sure it does.
Understand I've never done that before, but all the guide requires to be able to boot recovery to progress, and with that "FAILED remote dtb" error I'm getting I don't know how to go any further. The TWRP version i'm using "twrp-2.8.7.0-onyx_f2fs_r5.img" is supposed the be the right one for my phone.
I would also test stock recovery but I don't have an image file and so far no luck finding one.
KrapnoV said:
I would be very happy to flash a compatible rom this time, but while fastboot SEEM to work, i'm not sure it does.
Understand I've never done that before, but all the guide requires to be able to boot recovery to progress, and with that "FAILED remote dtb" error I'm getting I don't know how to go any further. The TWRP version i'm using "twrp-2.8.7.0-onyx_f2fs_r5.img" is supposed the be the right one for my phone.
I would also test stock recovery but I don't have an image file and so far no luck finding one.
Click to expand...
Click to collapse
Here is stock recovery image for E1005. https://drive.google.com/file/d/0B6zU7r3AtRjFb2tyQU11YTdLVEU/view?usp=sharing
Hi,
My phone OnePlus X E1003 was hard brick after install twrp.. now phone is dead..cannot access recovery and fastboot,screen blank and just vibrate.. when i plug in. it only detect qualcomm HS-USB driver.. but opx still dont have zip to repair the broken partition. anybody have ideal?pls help me.
Same problem here
apekgee said:
Hi,
My phone OnePlus X E1003 was hard brick after install twrp.. now phone is dead..cannot access recovery and fastboot,screen blank and just vibrate.. when i plug in. it only detect qualcomm HS-USB driver.. but opx still dont have zip to repair the broken partition. anybody have ideal?pls help me.
Click to expand...
Click to collapse
Same here, black screen only vibrates on holding power button for 10 seconds :crying:
apekgee said:
Hi,
My phone OnePlus X E1003 was hard brick after install twrp.. now phone is dead..cannot access recovery and fastboot,screen blank and just vibrate.. when i plug in. it only detect qualcomm HS-USB driver.. but opx still dont have zip to repair the broken partition. anybody have ideal?pls help me.
Click to expand...
Click to collapse
What did you do besides trying to install twrp? It would be difficult to brick by just flahshing recovery unless it was the wrong one.
Sent from my ONE E1005 using Tapatalk
If you can get it in bulk mode then you should probably try this http://forum.xda-developers.com/one...stboot-adb-t2835696/post55024864#post55024864
Ok...easy peasy....it happened to me too...Just open a ticket for a remote session with oneplus.....
They do mostly everything in about 45 minutes.
I tried everything too, nothing worked. Don't stress yourself out...They were good about it.
joey24z1 said:
Ok...easy peasy....it happened to me too...Just open a ticket for a remote session with oneplus.....
They do mostly everything in about 45 minutes.
I tried everything too, nothing worked. Don't stress yourself out...They were good about it.
Click to expand...
Click to collapse
pls help me how u manage to contact technical support?
Related
Already posted this 5 times on 3 sites and just not getting a lot of help. If it's bricked, fine, tell me. If it can be fixed, give me ideas.
I can't flash the bootloader or boot in any possible way. not through adb, not through tool kit, not through nexus 7 restore, nothing.
I can access fastboot mode (power+vol down) but nothing else. Standard power on gets stuck on google screen. It is unlocked. I have tried 3 different USB ports and 6 cables with no change.
No BS please, either Yes it's bricked sorry or No, it's not bricked, here are some ideas.
now i see that i'm not alone
same problem here, nobody ? It's a powerfull tablet, maybe now is going to be a powerfull paperweight, big paperweight, so sad.
can you boot into download mode if u can then
1.put your device into download mod 2.download the official firmware for your device on your computer
3.connect yor phone into your computer and flash it
if you can't boot into download mod then sorry I think it's bricked try to bring it to a service center
Sent from my SM-N7505 using XDA Free mobile app
pls answer me so I can help you
I couldn't help myself... I love my Nexus 7.
mrdownboy said:
I couldn't help myself... I love my Nexus 7.
Click to expand...
Click to collapse
LOL
and
zidozido22, i can boot just in fastboot mode
j4k0 said:
LOL
and
zidozido22, i can boot just in fastboot mode
Click to expand...
Click to collapse
Does the PC recognize? If you run the "fastboot devices" does it return a serial number? These things are pretty difficult to hard brick and if you can still get to the bootloader, then chances are it is recoverable. It helps to mention what you did for it to get to this state as well.
es0tericcha0s said:
Does the PC recognize? If you run the "fastboot devices" does it return a serial number? These things are pretty difficult to hard brick and if you can still get to the bootloader, then chances are it is recoverable. It helps to mention what you did for it to get to this state as well.
Click to expand...
Click to collapse
yes, it sends the serial number but when I had tried to flash it then it returns an error.
.***now im trying again with SkipSoft Android Toolkit, but it is stuck waiting for adb mode
before that state, it was charging, just that.
The tablet got Android 5 from OTA, and then android 5.1, i was using it as normal, but one day, while it was charging, it just show the google logo (name) and the lock down.
My 2012 wifi did that exactly. I downloaded wugfresh Nexus Root Toolkit yours can be d/loaded from here http://forum.xda-developers.com/showthread.php?t=2389107
All i did was put my 7 in fastboot mode then ran the tool kit. I then launched the advanced utilities and then fastboot format. Then i flashed stock rom.
Worked a treat. Thought mine was toast as well good luck.
snod33 said:
My 2012 wifi did that exactly. I downloaded wugfresh Nexus Root Toolkit yours can be d/loaded from here http://forum.xda-developers.com/showthread.php?t=2389107
All i did was put my 7 in fastboot mode then ran the tool kit. I then launched the advanced utilities and then fastboot format. Then i flashed stock rom.
Worked a treat. Thought mine was toast as well good luck.
Click to expand...
Click to collapse
I tried once, but i will try it again, thank you
---------- Post added at 12:25 AM ---------- Previous post was at 12:09 AM ----------
doing that you said:
Advanced tools--> fastboot format
now it is stuck in "Fastboot Formating CACHE..."
=(
i think the main problem (one o f them) is that i cannot use adb, when i use the command
Code:
fastboot devices
i get the serial number but when i use
Code:
adb devices
the results is nothing.
j4k0 said:
I tried once, but i will try it again, thank you
---------- Post added at 12:25 AM ---------- Previous post was at 12:09 AM ----------
doing that you said:
Advanced tools--> fastboot format
now it is stuck in "Fastboot Formating CACHE..."
=(
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but that's not a good sign. I haven't found anyone reporting success when it's having that issue. If you have exhausted the external possibilities such as drivers, USB cords, the PC, trying Windows and Linux, etc and still getting the same thing then that means the eMMC is probably messed up. Examples here:
http://forum.xda-developers.com/showthread.php?t=2602638
can you boot into bootloader if you can then navigate by using volume up volume down till you find the recovery and press lock button and factory reset
zidozido22 said:
can you boot into bootloader if you can then navigate by using volume up volume down till you find the recovery and press lock button and factory reset
Click to expand...
Click to collapse
They're way past the point that a factory reset would help or even work as wiping cache is not working and that is part of a factory reset. If it isn't wiping through fastboot commands, it definitely won't work through recovery.
sorry, then you should bring it to a service center
very hard and sad to hear that, thank you anyway guys...
about RMA i saw that will be expensive bcz the warranty time expired
OK So... I decided to root my TF103c (K010) so I remove some of the stupid crapware that asus has installed and I gained root fine and went ahead and started removing stuff. But apparently I removed something I shouldn't have and now I'm constantly getting Asus Services has stopped messages and I can't actually do anything with the damn thing. Because it has such a crap locked down recovery and bootloader etc. I can't seem to find any easy way around this. As in I can't just load all the things I uninstalled from the backups because I can't use ADB with the device. (Yes it WAS turned on in the settings until I formatted cache and data in case that might fix it... it didn't)
Does anybody have any advice?? Coz I'm stumped...
fastboot
RaVe-N said:
OK So... I decided to root my TF103c (K010) so I remove some of the stupid crapware that asus has installed and I gained root fine and went ahead and started removing stuff. But apparently I removed something I shouldn't have and now I'm constantly getting Asus Services has stopped messages and I can't actually do anything with the damn thing. Because it has such a crap locked down recovery and bootloader etc. I can't seem to find any easy way around this. As in I can't just load all the things I uninstalled from the backups because I can't use ADB with the device. (Yes it WAS turned on in the settings until I formatted cache and data in case that might fix it... it didn't)
Does anybody have any advice?? Coz I'm stumped...
Click to expand...
Click to collapse
are you still having problems? do you have a pc with adb installed and or fastboot?
---------- Post added at 12:19 PM ---------- Previous post was at 12:09 PM ----------
majored said:
are you still having problems? do you have a pc with adb installed and or fastboot?
Click to expand...
Click to collapse
ok well open a command window or if you have windows you can use powershell type adb devices enter anything? If that got you nothing while the device is powered on then power off device . With the device off press and hold vol up and power btton when device powers on release power button but continue holding vol up. if its charging the battery icon can mess this process up so unhook your device if your having problems you should boot to droidboot (aka FASTBOOT) where your adb commands will simply start Ex. fastboot devices it should read your device.
---------- Post added at 12:26 PM ---------- Previous post was at 12:19 PM ----------
majored said:
are you still having problems? do you have a pc with adb installed and or fastboot?
---------- Post added at 12:19 PM ---------- Previous post was at 12:09 PM ----------
ok well open a command window or if you have windows you can use powershell type adb devices enter anything? If that got you nothing while the device is powered on then power off device . With the device off press and hold vol up and power btton when device powers on release power button but continue holding vol up. if its charging the battery icon can mess this process up so unhook your device if your having problems you should boot to droidboot (aka FASTBOOT) where your adb commands will simply start Ex. fastboot devices it should read your device.
Click to expand...
Click to collapse
Well what i did was flash a recovery not compatible with my k010 but this did not stop me from booting to droidboot however my stock recovery for now is gone . my device was doing this too had about minute or so once powered on till it crashed. MY BLUETOOTH Went out and in my settings the on off would slide back and forth till it crashed but best buy sold me a 40$ one year warranty SUCKERS and asus installed a new one
majored said:
are you still having problems? do you have a pc with adb installed and or fastboot?
---------- Post added at 12:19 PM ---------- Previous post was at 12:09 PM ----------
ok well open a command window or if you have windows you can use powershell type adb devices enter anything? If that got you nothing while the device is powered on then power off device . With the device off press and hold vol up and power btton when device powers on release power button but continue holding vol up. if its charging the battery icon can mess this process up so unhook your device if your having problems you should boot to droidboot (aka FASTBOOT) where your adb commands will simply start Ex. fastboot devices it should read your device.
---------- Post added at 12:26 PM ---------- Previous post was at 12:19 PM ----------
Well what i did was flash a recovery not compatible with my k010 but this did not stop me from booting to droidboot however my stock recovery for now is gone . my device was doing this too had about minute or so once powered on till it crashed. MY BLUETOOTH Went out and in my settings the on off would slide back and forth till it crashed but best buy sold me a 40$ one year warranty SUCKERS and asus installed a new one
Click to expand...
Click to collapse
Thanks for the reply.
I have a adb and fastboot but most of the commands just don't work. I tried to remotely install apks but that fails. I tried to side load the latest FW downloaded from ASUS but it fails the certificate check. Basically I'm just waiting for the next system update to come OTA and I'll try flashing that... No idea when that will be of course...
Thanks for trying to help though.
Flashing Firmware using DROIDBOOT:
Instructions: https://drive.google.com/file/d/0B_JkvfrnO7pXMzVaZEM5OFF2ZGM/view
Download: https://yadi.sk/d/fduOPFuhes3dC or https://drive.google.com/file/d/0B_JkvfrnO7pXSHc1RGhzak1DN2c/view
(Fastboot incudled, partitions images in .img format, adb incudled, but not needed)
i dont have runned update_image.bat. i needed only recovery and system.
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash recovery recovery.img
fastboot flash system system.img
but you need to find some fastboot drivers for tablet.
i have used intel soc. drivers. but yet i dont have download link.
just google search to TF103C fastboot/driodboot drivers.
where's firmware
RaVe-N said:
Thanks for the reply.
I have a adb and fastboot but most of the commands just don't work. I tried to remotely install apks but that fails. I tried to side load the latest FW downloaded from ASUS but it fails the certificate check. Basically I'm just waiting for the next system update to come OTA and I'll try flashing that... No idea when that will be of course...
Thanks for trying to help though.
Click to expand...
Click to collapse
whare did you find firmware on asus site. i go to support and all i see is Kernel Code and manuals.
---------- Post added at 03:00 PM ---------- Previous post was at 02:55 PM ----------
Ok I fastboot flash 2.2.33.138. with no help from asus. but jacky_cao <[email protected]> got this reply i suggest you to contact the RMA center again . they will help you to update the firmware to (FW_WW_TF103C-2.2.33.144-release-user-20150827-signed.zip ) manually. But can't tell me how to contact anybody to help do that. does anybody here have the files needed to ota up to 144?
Guys, I followed the instructions from gouster3, but my Asus still hangs up during the boot. I just see the logo ASUS In search of incredible and that is it.
I too had a problem having foolishly erased an apparently needed system app after rooting. After many hours off and on of trying to sideload the latest firmware from ASUS i finally found this thread and success.
1) Of course put device in DROIDboot (fastboot). From power off, reboot tablet holding power + vol up for 2-3 seconds.
Per Post #4
[Cannot post url due to restrictions, get links from post #4. use the 2nd link in post, first link is dead]
(Fastboot included, partitions images in .img format, adb included, but not needed)
unpack zip and launch adb. (i already had an install of minimal adb and fastboot so I only moved boot, recovery, system, droidboot, flash, partition.tbl and AS-TF103C-v67.43-capsule.bin to that folder and launched from there. In hindsight I only probably needed system, flash, partition and capsule and might not have needed anything but system...)
fastboot erase system
fastboot flash system system.img
This takes a few minutes in which it appears nothing is happening... and then system is sent in 3 chunks.
Upon launch process.google.apps or something kept crashing and I could not log into google, but a reset from within the OS fixed that and I was back in business. I probably should have loaded recovery and cleared the cache and such and then rebooted, but i got hasty.
Anyway I know this is an old problem and people have probably moved onto other things, but for someone like me who has had this once wonderful device sitting around waiting for a new breathe of life and the energy to take another stab at it out, don't give up. And thanks to all the gurus here for all the help over the years...
gouster3 said:
Flashing Firmware using DROIDBOOT:
Instructions: https://drive.google.com/file/d/0B_JkvfrnO7pXMzVaZEM5OFF2ZGM/view
Download: https://yadi.sk/d/fduOPFuhes3dC or https://drive.google.com/file/d/0B_JkvfrnO7pXSHc1RGhzak1DN2c/view
(Fastboot incudled, partitions images in .img format, adb incudled, but not needed)
i dont have runned update_image.bat. i needed only recovery and system.
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash recovery recovery.img
fastboot flash system system.img
but you need to find some fastboot drivers for tablet.
i have used intel soc. drivers. but yet i dont have download link.
just google search to TF103C fastboot/driodboot drivers.
Click to expand...
Click to collapse
THANKS I bricked my tf103c and this fixed it and got it working again
Do you have any easy guide on installing a custom rom to this device in this way?
I use Zenfonerootkit_20150528 to root the device and it works fine
I just can never find a rom or such or guide on this :/ ( i found this old device and thought i would have a mess with it)
I
Hello everyone
I hope you all are around I really need your help at it again, I have got an asus tf 103c i tried to root it and now I get a bootloop i tried everything but failed. Please I know you will be angry because you already explained everything but I am a verry beginner and also many links are dead I need your help.
Thank you from advance
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
lucasnoman said:
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
Click to expand...
Click to collapse
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
moto999999 said:
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
Click to expand...
Click to collapse
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
Yes, I did it. But a blue screen appear fast and my smartphone turns off. It does not go into recovery at all, only after I start the phone normally. Funny that I only get message of success since the release of the bootloader until the installation of twrp.
Have you tried "fastboot boot <recovery.img>"?
sudloa said:
Have you tried "fastboot boot <recovery.img>"?
Click to expand...
Click to collapse
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
lucasnoman said:
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
Click to expand...
Click to collapse
fastboot could use in fastboot mode (shutdown then vol down + power) only and windows sohuld recognize this.
But I think your adb usb driver got conflict somehow.
You can try "usbdeview" to uninstall all adb usb drivers then use some knid of universal adb usb driver installer.
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
lucasnoman said:
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Click to expand...
Click to collapse
Hi, You should TITLE your post Why does TWRP not stay resident ?
paulsnz2 said:
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
Hi, You should TITLE your post Why does TWRP not stay resident ?
Click to expand...
Click to collapse
You're Welcome
Antisound said:
You're Welcome
Click to expand...
Click to collapse
I have the 820. Could NOT get windows to see this phone on stock rom. Don't recall exact steps I took, but I do remember the ADB feature within TWRP saved my day. Windows would see the phone in TWRP recovery adb mode, but could never get windows to adb connect with stock rom.
Hey people, sry I'm coming back now. Lightning struck my street and burned my pc. But I come back with another problem, when I connect my phone to the pc nothing happens. I mean, I can't transfer cause MTP doesn't work. I tried install unninstall and install again adb, and all the drivers but it did not work. So I'll need to fix this to try to install twrp again
Guys! I was being too stupid! I found my mistake... I was using another smartphone twrp... So, for who are having same issue, pay attention to this. But, thanks everybody and sry for this hahaha
Hi !
I've attempted to deal with the devil by trying to root my Pioneer XDP-300R resulting in a bootloop problem (device is stuck on "Powered by Android" screen).
I attempted to flash a boot.img for a Onkyo DX-P1 (which is the same firmware), and still I haven't progressed.
No firmware, update or imgs are provided on Pioneer's website.
I still have access to fastboot (OEM is LOCKED, so I can't boot TWRP and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
Edit :
I managed to make my device go into Qualcomm's emergency download mode.
Here's how to :
1 - Make sure the device is completely off and unplugged from USB.
2 - Install QPST V2.7.474 (not enough posts to share url, but I can PM it).
3 - Install QDLoader Drivers (same as #2).
4 - Simply press and hold the "Play" button while connecting it to your computer, the device manager should see a "Qualcomm 9008 port" listed in Ports while the player's screen stays black.
5 - Do the Carlton (important step !)
Now, if anyone possessing a FUNCTIONAL AND ROOTED Pioneer XDP-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All I would need from you is some time, hard disk space and patience to sort it out.
Please <insert_your_name_here>, you're my only hope !
Edit #2 :
Thanks to minotauri's great help, we managed to get a FULL rom backup, split the partitions to files and generate all the files needed for QFIL.
ErrOzz has been given access to this, hoping that he'll try it out soon.
If that works, I'll link you the files and write the walkthrough to bring you DAP back to life.
minotauri's contributions are not in rest tho, he managed to also successfuly patch TWRP for the device, so anyone can securely flash things from there now.
For anyone reading this thread : you're not the only one who screwed things up, we did too but we might have the cure. Hang in there !
grogcw said:
Hi !
I've attempted to deal with the devil by trying to root my Pioneer XDP-300R resulting in a bootloop problem (device is stuck on "Powered by Android" screen).
I attempted to flash a boot.img for a Onkyo DX-P1 (which is the same firmware), and still I haven't progressed.
No firmware, update or imgs are provided on Pioneer's website.
I still have access to fastboot (OEM is LOCKED, so I can't boot TWRP and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
Edit :
I managed to make my device go into Qualcomm's emergency download mode.
Here's how to :
1 - Make sure the device is completely off and unplugged from USB.
2 - Install QPST V2.7.474 (not enough posts to share url, but I can PM it).
3 - Install QDLoader Drivers (same as #2).
4 - Simply press and hold the "Play" button while connecting it to your computer, the device manager should see a "Qualcomm 9008 port" listed in Ports while the player's screen stays black.
5 - Do the Carlton (important step !)
Now, if anyone possessing a FUNCTIONAL AND ROOTED Pioneer XDP-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All I would need from you is some time, hard disk space and patience to sort it out.
Please <insert_your_name_here>, you're my only hope !
Click to expand...
Click to collapse
Hi - I saw your post on Head-Fi (antdroid over there). Let me look into this!
Here is a bunch of system dump images and qcn files: https://drive.google.com/drive/folders/1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV?usp=drive_open
Hello.
How can I write boot from qdload 9008 state?
Hi !
From the edl / qdload 9008 state, you can't afaik.
Here's how I think you can :
1 - Unplug your device from USB and power it off from whatever state it is.
2 - Power it on pressing Power + Previous button (keep holding, you should be "stuck" on the penguin logo).
3 - Connect your USB.
4 - Check that you have a Android ADB Device in your device manager (install drivers manually if you have an Unknown device).
5 - Grab any fastboot from the internet if you don't already have it (I'll PM you my gdrive, it's there for exemple).
6 - From CMD, go to fastboot directory. (cd <my_folder_with_fastboot>).
7 - Type in : fastboot devices
If fastboot sees your device, you're on the good path, else, check your driver / connection / reboot to fastboot "penguin" state.
8 - Type in : fastboot oem device-info
If it replies
(bootloader) Device unlocked: true
among others, you're in a good, good way, else, you're screwed by now, but we are working on it.
9 - If all the precedent are fulfilled type :
fastboot flash boot <my_boot_image.img>
10 - Mandatory Carlton.
I hope you'll be in the right path all the way, if you're stuck somewhere or if your bootloader is locked, please let me know.
Cheers !
ErrOzz said:
Hello.
How can I write boot from qdload 9008 state?
Click to expand...
Click to collapse
I was successful in creating a recovery (twrp) for this device.
https://www.antdroid.net/2019/02/pioneer-xdp-300r-root-twrp-recovery.html?m=1
also created a XDA thread here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949
Feel free to PM me if you have questions or we can work it through here
Hi,
I have the same problem. I am able to get qdload 9008 state from here now. However, after unplug and followed grogcw's hints, the device is not recognized again. Also, the device hasn't ennobled debug mode before too. All the adb and fastboot commands return no device.
Hopefully can get more help here.
---------- Post added 28th February 2019 at 12:16 AM ---------- Previous post was 27th February 2019 at 11:58 PM ----------
minotauri said:
I was successful in creating a recovery (twrp) for this device.
https://www.antdroid.net/2019/02/pioneer-xdp-300r-root-twrp-recovery.html?m=1
also created a XDA thread here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949
Feel free to PM me if you have questions or we can work it through here
Click to expand...
Click to collapse
Is there anyway to flash TWRP and so with QDLoader?
I believe he is on vacation for another week and half. If you haven't enabled the bootloader unlock option within Android, then my recovery method may not work since it may not let you flash the recovery.
You can try to fastboot boot recovery.img though
Hi ! I'm back from vacation, but I still haven't my device around.
Any user willing to test are welcome to reply or PM me !
Let's have all the bricked units working, shall we
grogcw said:
Hi ! I'm back from vacation, but I still haven't my device around.
Any user willing to test are welcome to reply or PM me !
Let's have all the bricked units working, shall we
Click to expand...
Click to collapse
How can we get started?
We actually did start probing stuff around, and we are missing something in the "full restoration process", so we're stuck for now.
Sahara protocol still is a mystery for us, and we can't get pass an error.
I think we don't actually have the right programmer_firehose.mbn for our device, but if it's not this, I'm basically out of ideas. (we might need an "QFIL expert" on this)
I still don't have my device around and feeling dumb about this.
Anyway, all the files and tools required to try probing around are in my gdrive and I can PM the link (as I still can't post it right away) if anyone is interested.
Thanks for trying to help or actually help everyone !
Cheers !
Hello,
I try to root my xdp-300r,after reboot have bootloop result.
I don't know how to reflash systme.img.
can suggest any repair plan,thank you~
Was able to unbrick device. Here are the steps TO DO IT
grogcw said:
hi !
I've attempted to deal with the devil by trying to root my pioneer xdp-300r resulting in a bootloop problem (device is stuck on "powered by android" screen).
I attempted to flash a boot.img for a onkyo dx-p1 (which is the same firmware), and still i haven't progressed.
No firmware, update or imgs are provided on pioneer's website.
I still have access to fastboot (oem is locked, so i can't boot twrp and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
edit :
i managed to make my device go into qualcomm's emergency download mode.
Here's how to :
1 - make sure the device is completely off and unplugged from usb.
2 - install qpst v2.7.474 (not enough posts to share url, but i can pm it).
3 - install qdloader drivers (same as #2).
4 - simply press and hold the "play" button while connecting it to your computer, the device manager should see a "qualcomm 9008 port" listed in ports while the player's screen stays black.
5 - do the carlton (important step !)
now, if anyone possessing a functional and rooted pioneer xdp-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All i would need from you is some time, hard disk space and patience to sort it out.
please <insert_your_name_here>, you're my only hope !
edit #2 :
thanks to minotauri's great help, we managed to get a full rom backup, split the partitions to files and generate all the files needed for qfil.
Errozz has been given access to this, hoping that he'll try it out soon.
If that works, i'll link you the files and write the walkthrough to bring you dap back to life.
Minotauri's contributions are not in rest tho, he managed to also successfuly patch twrp for the device, so anyone can securely flash things from there now.
For anyone reading this thread : You're not the only one who screwed things up, we did too but we might have the cure. Hang in there !
Click to expand...
Click to collapse
i was able to unbrick my device
dantuko said:
all credits go to anthony nguyen aka minotauri. Thank you!
requirements:
samsung drivers installed
windows 10 (i have the windows 10 pro installed)
oem unlock
usb debbuging selected prior to brick
install the latest samsung drivers
install fastboot/adb drivers
stock-boot.img provided by minotauri
the steps are as follows:
the device must be in recovery mode an plugged to the computer. I was on stock recovery
open device manager in windows, look for anything android and delete it and choose to delete the drivers
refresh device manager for new devices (keep only the xdp-300 android connected)
right click on the android device and click on update drivers
select browse my computer for driver software
click on let me pick from a list of available drivers
unselect show compatible drivers (if you see a samsumg driver here, select it. If not try generic windows adb drivers)
seletct google adb drivers (this is the one that worked and it's under samsung drivers)
i performed the steps 1 through 8 a few times until the computer categorized the device as adb
open a command prompt, navigate to the directory where fastboot is installed and type: Fastboot devices (you should have a device listed here)
type: Fastboot oem unlock (this unlocks the bootloader)
after copying stock-boot.img to the root of the your fastboot directory, type: Fastboot flash boot stock-boot.img (reboot)
after the reboot you should see normal boot
if you want twrp and root follow the instructions here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949 all credits go to anthony nguyen.
i installed twrp the latest supersu pro, viper4android, root browser, busy box pro and everything works perfectly.
:fingers-crossed::fingers-crossed::fingers-crossed:good luck to you e n j o y ! ! !:fingers-crossed::fingers-crossed::fingers-crossed:
i am not an android programmer so i won't be able to help you from that perspective, but i a software engineer so i maybe able to answer some questions.
There is no guarantee this method will work for you but it did work for me
I can provide a TWRP backup file for you to restore your device
Click to expand...
Click to collapse
I have a rooted xdp300r rooted
ralf05 said:
Hello,
I try to root my xdp-300r,after reboot have bootloop result.
I don't know how to reflash systme.img.
can suggest any repair plan,thank you~
Click to expand...
Click to collapse
It was bricked and I was able to fix it and root it
Help !!!
Hello
Gentlemen, help me! I've broken my device
I hit the whole system on my xdp300r. What can I do in this case ??? Only I can turn on TWRP and nothing more.
[email protected]
---------- Post added at 05:55 PM ---------- Previous post was at 05:51 PM ----------
dantuko said:
i was able to unbrick my device
Click to expand...
Click to collapse
Help !!!
dantuko said:
i was able to unbrick my device
Click to expand...
Click to collapse
Hello
Could I ask you for a backup file? Unfortunately, I lost the systemThank you very much.
Greetings.
[email protected]
stefan999 said:
Hello
Could I ask you for a backup file? Unfortunately, I lost the systemThank you very much.
Greetings.
[email protected]
Click to expand...
Click to collapse
I UPLOADED THE BACKUP FILE TO MY GOOGLE DRIVE
https://drive.google.com/drive/folders/1vM7Z12w3CsbutSr54lY4tTdzyN1jurpp?usp=sharing
dantuko said:
I UPLOADED THE BACKUP FILE TO MY GOOGLE DRIVE
https://drive.google.com/drive/folders/1vM7Z12w3CsbutSr54lY4tTdzyN1jurpp?usp=sharing
Click to expand...
Click to collapse
Here is a few items to note about the image:
You must have twrp installed and accessible in order to restore this image.
First time booting after the restore will take a long time, so have a cup of coffee and let it do it's thing.
Every time you boot the OS will perform application optimization, it doesn't bother me so I have not even looked into it.
After you boot connect to your WIFI and open Google Play to set up your account
If you want to use Viper4Android, download and install busybox, then open settings, go to apps and disable Musicfx, then reboot and turn Viper4Android on.
Good luck
dantuko said:
Here is a few items to note about the image:
You must have twrp installed and accessible in order to restore this image.
First time booting after the restore will take a long time, so have a cup of coffee and let it do it's thing.
Every time you boot the OS will perform application optimization, it doesn't bother me so I have not even looked into it.
After you boot connect to your WIFI and open Google Play to set up your account
If you want to use Viper4Android, download and install busybox, then open settings, go to apps and disable Musicfx, then reboot and turn Viper4Android on.
Good luck
Click to expand...
Click to collapse
Thanks for answer and sharing your files. Unfortunately, there is some error when trying to restore in TWRP.
I packed all the items from your disk in ZIP and downloaded to the SD card .
I'm getting an error about the content: no MD5 file found Failed to map file'/external_sdxxxxxx-Full BACKUP.zip'
Error instaling zip file
. Do you have an idea why this is happening?
twrp settings
stefan999 said:
Thanks for answer and sharing your files. Unfortunately, there is some error when trying to restore in TWRP.
I packed all the items from your disk in ZIP and downloaded to the SD card .
I'm getting an error about the content: no MD5 file found Failed to map file'/external_sdxxxxxx-Full BACKUP.zip'
Error instaling zip file
. Do you have an idea why this is happening?
Click to expand...
Click to collapse
You need to change settings in twrp not to check md5 checksum, if it doesn't work then i'll create one with checksum.
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?