fastboot can't see my dev phone 1 - G1 Q&A, Help & Troubleshooting

Hello,
I posted this on cyanogenMod forum few days ago, but no one was able to help me so far, so maybe I will have more luck here...
Recently I found my old dev phone 1 with stock image and decided to make it more useful by installing cyanogenMod on it. I tried to follow instructions on http://wiki.cyanogenmod.com/index.php?title=Android_Dev_Phone_1:_Full_Update_Guide page. I downloaded Amon_Ra's Recovery, adb and fastboot tools, added all-htc udev rules and followed instructions on fastboot page http://wiki.cyanogenmod.com/index.php?title=Fastboot#Access_bootloader to access the bootloader.
Unfortunately fastboot devices returned empty list of devices even more, lsusb did not list any new device.
When connecting the phone in debug mode adb sees my phone without problems and lsusb shows my phone as well so it's not connectivity problem.
I found this section about SPL S-OFF on fastboot page http://wiki.cyanogenmod.com/index.php?title=Fastboot#Verify_SPL_S-OFF and it seems it applies to my case as my fastboot screen looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The section continues that in such case I have to use different SPL, so I went to http://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_DangerSPL page to install DangerSPL, but it requires Amon_Ra recovery which again requires fastboot to install so there's a cycle here
I would be grateful for any hints what I should do in this situation
Thanks!

ok, never mind: I used standard dream procedure with rooting and it worked ok, I'm on cyanogenMod now
Cheers
Morg

Related

OPO stuck on recovery mode loop and PC won't recognise it in order for me to flash it

So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!
Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!
Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk

System(MM) update problem.

On 5.1.1 build LMY48T
When I received this phone on 16Nov I tried to let do the update to MM. It would D/L but fail in updating. (Just reboot after each try) I went ahead with 5.1.1 in unlocking and rooting with no problem. tried to allow it to update date again as it has been requesting and it now justs boots into TWRP. I wish to upgrade to MM but am stymied. Need Guru assistance.
First time around it might have been a corrupt download. Now it's because you're rooted and have TWRP installed. To be able to update through OTA your system needs to be fully stock.
To update now you need to flash a factory image (plenty of guides if you search). I recommend using fastboot, but you could also use a toolkit (Nexus Root Toolkit). If you don't want to wipe your phone, leave out the userdata image when flashing (or the "no wipe"-mode in NRT).
I did search but I have to admit I got alittle confused as there seemed to be different factory versions available. I did do updates to my Note 2 until they sneakily locked the bootloader on me (verizon Bastages) I will look at the guides more throughly now to educate myself better. Thank for the guidance.
Which one?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Either of them will work, bu to save you time, get the latest (MRA58R) because it's just going to prompt you to install those.
Following the advice my N6 is rocking MM and rooted. Thanks to all.
Awesome! Glad you got it working!

Bricked my CM G1, need to flash in QPST or miflash?

So I bricked my CM android one 2nd gen and it's not booting up, I can only see boot page like forever.
How did I come to this?
I cleared the cache in recovery then it somehow corrupted the /cache folder.
What I forgot to do is I did not enable OEM unlocking in settings so I cannot flash anything in flashboot and adb.
I'm stuck because my phone is
1. Not rooted
2. Bootloader locked
3. No custom recovery
4. Stock Android
What I plan to do now is to use the QPST or miFlash, I have already installed the necessary drivers and I can see my phone detected in download mode (using COM port)
My problem is I don't know where to look for the files needed. Or I'm not sure if these are the correct files I need because I just got the screenshot from other qualcom based phones. But I want to try it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kindly help me please where can I get these files?
prog_emmc_firehose_8974.mbn
settings.xml
MPRG8974.mbn
8974_msimage.mdn
rawprogram0_64G.xml
patch0.xml
Thanks in advance
Or you are free to suggest other methods if you have
Try this bro
They have all the xml files you needed as well as the right rom for those tools. You can also download the tool their using flash its easier and better. Let me know if you succeed.
http://forum.turkdevs.com/konu-6-0-1-stock-qfil-dual-general-mobile-android-one-4g-mmb29k.html?pid=95110
Incase you dont have an account lemme give you the gdrive link for the rom with the xml files.
https://drive.google.com/file/d/0B065LdNGqJLGM1BoZWNxbTFBSDA/view
Password: forum.turkdevs.com
Goodluck kabayan! :good:
I'll try this method but it says
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
:'(

Novacom Drivers and Touchpad Toolbox

Hello everyone, I was trying to use TPToolbox with this topic : https://forum.xda-developers.com/showthread.php?t=2756314
On the "Loading TPToolbox" section, I have troubles.
I have put my tablet on recovery mode, I have installed the drivers (not without a couple of hours of research.....)
I launched "tptb_v42_win.bat", a cmd window appears, and here is my problem :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It cant finds novacomd service, so I imagine that's a problem with the drivers, or something like this, so, please, I need help
(Sorry if my english is bad, I'm french).
Patahuete said:
Hello everyone, I was trying to use TPToolbox with this topic : https://forum.xda-developers.com/showthread.php?t=2756314
On the "Loading TPToolbox" section, I have troubles.
I have put my tablet on recovery mode, I have installed the drivers (not without a couple of hours of research.....)
I launched "tptb_v42_win.bat", a cmd window appears, and here is my problem :
It cant finds novacomd service, so I imagine that's a problem with the drivers, or something like this, so, please, I need help
(Sorry if my english is bad, I'm french).
Click to expand...
Click to collapse
All the drivers and tools you need should be here
Thanks you, but, I have used the UniversalNovacomInstaller but, i'm stuck on that :
I've launch the process 3 hours ago, and, it's always the same thing, I'm stuck on this.
Ok, thanks you, I've finally do it ! Android is on my Touchpad <3

Question Fastboot stuck on "waiting for device". Whatever OS I use.

Hi there,
I have just purchased a Zenfone 8, the bootloader is unlocked (I have the ugly message saying that the phone can"'t be trusted because bootloader is unlocked bla bla bla at startup).
However, while adb works, I can't get fastboot to recognize my device.
I tried on W10 and 11, also on Linux Mint.
Other phones are recognized properly by fastboot, but not the zenfone 8. And of course, fastbootd doesn't work.
Anyone faced this issue?
Thanks,
Anghi
Look inside here:
Fastboot Mode ASUS Zenfone 8, how to - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can get into fastboot mode. Using combo key or even "adb reboot bootloader". But on this screen, then fastboot does not recognize the device
And I have tried both bootloader (in principle fastboot) and fastbootd (the one within the recovery) screens. Fastboot commands don't work under both screens.
I think to get fastboot working I had to install the Asus specific driver on my pc
Ok thanks. Let me try.
Okay, solved by trying several USB C wires.
Thanks for the advices and help!

Categories

Resources