Hi trusty XDA-peoples... I've been on the modaco forums the past 12 hours and have had no luck. I have a bung Desire after following the Apps2SD update (the goldcare and root went 100% fine). I used the old method and have just tried Paul's new method. The result is the same (I've tried it in 3 different Linux distros, it still says "device not found"). I'm only getting this 'device not found' AFTER I applied the A2SD zip update on the modaco forum (first page on the root instructs).
http://i40.tinypic.com/6t22w6.jpg
If anyone can help, that'd be much appreciated. The phone was on the red-triangle when this error occurs, and I've also tried it on the "different screens" (which doesn't make sense but I tried them anyway - on hboot screen and fastload screen) - still "device not found"...
Please Help.
Thanks guys.
You try starting over from the very beginning?
And, I think you might be right about A2SD breaking root.
eViL D: said:
You try starting over from the very beginning?
And, I think you might be right about A2SD breaking root.
Click to expand...
Click to collapse
I have gone all the way back. I have no problems flashing TestRUU (the "new method" also works) but when ADB tries to load the Recovery on to my phone, "device not found" (yep I'm SU all my commands so I don't think it's a permissions problem). It just won't see my phone in the mode where the red-triangle is up. It's just dead.
Anyone think replacing TestRUU with Rootedupdate.zip and then flashing that way will work? Or will that completely brick it?
Ok, was gonna suggest
./adb-linux kill-server
sudo ./adb-linux start-server
sudo ./recovery-linux.sh
try a different port?
eViL D: said:
Ok, was gonna suggest
./adb-linux kill-server
sudo ./adb-linux start-server
sudo ./recovery-linux.sh
try a different port?
Click to expand...
Click to collapse
Tried 3 different machines, 2 Ubuntu builds and Paul's TinyCore new-method. USB ports appear to work OK (since it flashes TestRUU fine on the USB cable/ports!)
I've tried testing all the adb settings (adb reboot/root/usb etc.) but all come up "device not found". Grr. It appears Apps2SD broke the Recovery mode on my Desire? How is that even possible?
Ok, so what is the last thing you have done that worked?
almost crapped my pants....
Got this error just now.
error: device not found
error: device not found
[email protected]:~/android/tools/pushfiles$ error: device not found
unplugged the usb and plugged back in and reran the command and it worked.
are you using a hub?
eViL D: said:
Ok, so what is the last thing you have done that worked?
Click to expand...
Click to collapse
Last night, ROM updated with Paul's Root. No problems. Then I ran through the recovery-linux.sh and got green recovery screen on desire. Installed A2SD.zip from my 4gb Goldcard. Reboot. Fine.
Then turn off phone, removed 4gb goldcard and inserted 8gb normal card. Rebooted with recovery-linux.sh and got recovery screen on Desire. Partitioned 8gb card into 512mb and 7.5gb partitions. converted from ext2 -> ext3, reboot.
That's where it's broken. Boot- Loop at "quietly brilliant". Rebooted a few more times, and same. Removed 8gb and inserted 4gb goldcard. Same looping problem.
Then tried to reflash Pauls' rooted ROM - but can't get into the recovery screen anymore. And this was the first time I saw in Terminal "device not found". Ever since then it's been 'device not found'
Tried to reinstall TestRUU from windows, failed. Couldn't see the phone.
After a few hours, did a clear-storage from bootloader., this time (i think i had 8gb card in) the phone loaded with no looping. But the ROM is broken. Cannot detect SIM and cannot detect SD Cards (goldcard is no go either). Only thing that works is WiFi at the moment.
Downloaded Pauls' r3 new method and reflashed. First process worked fine, everything flashed (i got a strange error that I posted on modaco about: "FAILURE hboot 90 pre-release? please flush <something else>". The error was on r2 and Paul looked into and updated something and posted r3. I flashed via r3 and still got the same error! But some other system files continued to flash (not sure what Paul fixed, but he did something). So I thought it was all good. step1.sh seem to go fine, but when i get to step2.sh - BAM! "device not found". Back to square one.
eViL D: said:
almost crapped my pants....
Got this error just now.
error: device not found
error: device not found
[email protected]:~/android/tools/pushfiles$ error: device not found
unplugged the usb and plugged back in and reran the command and it worked.
are you using a hub?
Click to expand...
Click to collapse
no hub, straight into usb port (even at the back of usb motherboard connection)
i'll try again
nothing :|
united we stand...
Hi biliskner!
Fear not - I'm sure we'll get your phone sorted - I have *exactly* the same problem, and it went wrong at the same place... usb works fine, but adb refuses to work, regardless what PC I use. Aaand, the same problems with sim card/sd card in the phone - I'm so glad (sorry!) that I've found someone else with the same issue!
Spent quite a long time in IRC with Paul and SGT somebody from MoDaCo trying a few things - they're both confident we'll get it fixed, just not quite sure how yet!
Seb
Any way you can test the usb/cable with something else?
sebm said:
Hi biliskner!
Fear not - I'm sure we'll get your phone sorted - I have *exactly* the same problem, and it went wrong at the same place... usb works fine, but adb refuses to work, regardless what PC I use. Aaand, the same problems with sim card/sd card in the phone - I'm so glad (sorry!) that I've found someone else with the same issue!
Spent quite a long time in IRC with Paul and SGT somebody from MoDaCo trying a few things - they're both confident we'll get it fixed, just not quite sure how yet!
Seb
Click to expand...
Click to collapse
Cool - there's someone else in the modaco forum, kingoffail, also having the exact same problem. We can't get into recovery mode. And the current ROM on it is totally useless :| (is the current ROM on it like a pre-build / testing ROM? No SD detect or SIM detect? Sounds like a bloody iPad!). I don't want an HTC (or any) iPad -.-
eViL D: said:
Any way you can test the usb/cable with something else?
Click to expand...
Click to collapse
I just reloaded it on my laptop with Ubuntu (the SDK tools -> recovery-linux.sh method). Same deal as last night. Tried 3 USB ports and different usb cable (not the original HTC cable). And ... "device not found".
I'm just about to try and flash a generic rom to it now, see if that fixes it.
also eViL D: yes - I'm confident the usb cables works absolutely fine as everything else works; just adb doesn't.
Seb
Well, you could fastboot the system image and boot image from the test ruu.
That sounds promising - how do you flash the /system bit?
sebm said:
I'm just about to try and flash a generic rom to it now, see if that fixes it.
also eViL D: yes - I'm confident the usb cables works absolutely fine as everything else works; just adb doesn't.
Seb
Click to expand...
Click to collapse
I understand. Just trying to get low level things first.
If I delete Paul's "TestRUU" and rename his "rootupdate.zip" to "TestRUU" and hack it that way, you think the step1.sh will flash it OK? (makes the step1.sh think it's flashing TestRUU but in fact it is flashing the rootupdated.zip rom which the might solve the problem?)
I don't understand why Paul has flashed a TestRUU before loading Recovery and then flash rootupdate.zip from the SDCard - why not just flash rootupdate.zip from Linux at step 1 and bypass TestRUU and trying to push Recovery from Linux into Desire's SDCard? Is that where the exploit is?
OK, we have some progress - I'm in the process of flashing RUU-MoDaCo-Bravo-1.15.405.4-release (I extract the zip from that archive, and am flashing with fastboot now) - something is happening at least!
Seb
Okay so,
I feel like this one's on the medium level of emergency here,
The issue is I flashed my cache, dalvick, factory reset, and (not sure) system to install Simple CM9, everything rolled along nicely except......
After booting into my promising new life, I noticed several issues:
KFU no longer recognized it, though the drivers still read "Android ADB Interface" in my computer
Google Apps would not sync my data, but still allows me to download apps from the play store
The sd Card partition no longer is shown by the OS, but still shows up when connected with usb (i'll be downloading a file manager soon, so this may answer itself to whether or not I can still access it)
TWRP will not boot by means of pressing the power button during initial boot
I understand I could solve my GAPPS sync problem by flashing them, and all my other problems wouldn't matter then. but I still have no means to flash'em.
Any and all help is GREATLY appreciated!
-a lowly noob
P.S. Everything about the ROM is fantastic except for those issues, (which are probably my fault) so many thanks on that end
P.P.S. (I do have a nandroid of my stock os before I wiped so If all else fails I can just go back to that if TWRP can be accessed and start over)
I seen a similar issue earlier and the guy fixed it by reinstalling the twrp
but u can always try going to reboot and select recovery and see if that works
gracci
That's a step in the right direction, thank you
no problem glad I could help
OS: Jellybean 4.3 to CM10.2 nightly
Device: n7015 (just to clarify)
Recovery: Clockwork Mod 6.0.3.1
Carrier: Optus
Country: Australia
So, I installed CyanogenMod. I followed the guide on the Wiki to the letter, repeating steps as necessary when it confused me. Got it installed fine in the end.
However...
1) I can't get mobile data. So I went into settings and did some poking, and when I try to enter "Manage mobile plan", it tells me to insert the SIM and restart. I didn't even touch the SIM during the install. I've since pulled it out, given it a look, put it back.
2) This one's very specific: When I turn off the phone while it's charging (not sure if it has to be by PC - I can't test by adapter), it will appear to crash while trying to load the battery icon to tell me how charged it is. This prevents the screen turning off until I restart the phone. Note this doesn't prevent it from charging.
Never happens if it's not on charge when I turn it off. Has never happened before installing CM.
3) A minor-ish bug, when I use the Cyan Delta app to try and update the OS, it reboots into CWM and generates these errors:
SD Card marker not found.
Error processing ROM Manager script.
Unrelated: CM is magical, I can edit the contents of my phone from Windows Explorer. This alone makes all this hassle worth it.
Hi,
I have followed the official wiki to install Cyanogenmod 12.1 nightly builds (December 25, 2015 nightly build) on my xperia M. It all worked well for the first time.
But suddenly after using it for some days happily, when I rebooted the device, the moment the device boots up, all the apps start crashing, causing the device unusable. I tried to reboot but it's still there. So I tried to repeat the process to get rid of this and tried to flash the December 30, 2015 build but somehow it is not working.
When I sideload the update zip file, it starts and gets stuck at 47% for quite long time and then suddenly finishes with (Total xfer: 1.00x ). The instant it goes 100%, the android icon showing "update" process disappears and screen keeps blinking and stays dark but still "adb devices" shows my device connected but the device screen just keeps blinking and nothing shows. I tried "adb reboot" but it throws this error
"error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
the "kill-server" command fails as well and thus, the problem persists.
I also installed open gapps after installing CM12.1 on the very first time. But in all those re-flashes, I skipped flashing it altogether and wiping cache partition, media and data & factory reset, these apps (calendar, music and gmail etc) throw the error the devices boots up. I guess the device is not getting formatted properly and its not being flashed with just the newer image. It gets stuck at 47% for way too long (almost 20 mins or more), while if I remember correctly, it didn't do so on first flashing.
Since I can't use any app when the device is ON, I can't open settings to check anything. Please help me getting rid of this, so that I can enjoy using this awesome ROM.
Thanks in advance.
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.