Related
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
Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!
I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!
Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...
You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.
thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?
If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.
Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...
mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse
I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...
Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!
have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse
right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day
You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.
Hey there, I think I've bricked my device and naively thinking it would be pain-free and careless as it was in my DHD, it was an utter brain melter with it's little brother device and I've spent the past 2 days frantically trying to fix it, probably making it worse.
Here's the problem:
- USB responds on PC with notification, doesn't seem mounted
- Unable to access any form of recovery/bootloader
- Attempted VM RUU but at the end it has a 101: File read error, even though the file is intact.
- Attempted latest RUU amongst various others, with an image write error.
- Loaded fasboot via PC & flashed downgrade from http://alpharev.nl/ - although flasher said it was 'successful' the RUU mentions 2.0.x-something and fails again
- Now a black screen that doesn't even show 4 corner error.
So yeah, I'm so lost right now. Any help at all is appreciated, since it's so messed up might as well try experimental methods of recovering this. Thanks a lot.
deolol said:
Hey there, I think I've bricked my device and naively thinking it would be pain-free and careless as it was in my DHD, it was an utter brain melter with it's little brother device and I've spent the past 2 days frantically trying to fix it, probably making it worse.
Here's the problem:
- USB responds on PC with notification, doesn't seem mounted
- Unable to access any form of recovery/bootloader
- Attempted VM RUU but at the end it has a 101: File read error, even though the file is intact.
- Attempted latest RUU amongst various others, with an image write error.
- Loaded fasboot via PC & flashed downgrade from http://alpharev.nl/ - although flasher said it was 'successful' the RUU mentions 2.0.x-something and fails again
- Now a black screen that doesn't even show 4 corner error.
So yeah, I'm so lost right now. Any help at all is appreciated, since it's so messed up might as well try experimental methods of recovering this. Thanks a lot.
Click to expand...
Click to collapse
Option A: Create a goldcard (you can use your DHD, or if you alread yahve one use that goldcard) and flash the latest WWE RUU (Link on my guide)
Option B: Less safe. Use the 2.3.3 RUU (Link on my guide)
Hey guys, searched for a while now but couldn't find a similar thread to this related to our phone.
Suddenly,
my Wlan stopped working.
The issue is well known, it starts up, says "unable to scan for networks" and shuts down.
Same goes for setting up a W-Lan hotspot, starts up and immediately after it stops trying.
Both worked flawlessly before.
Since then, i tried cache wipes, reboots etc.
I am on the newest dz radio, using Virtuous Sense 2.0.0 for sum time now.
I found a workaround for a galaxy s that implied deleting the configuration file. This file seems to be at a different location on the desire z. Additionally, it probably has a different filename.
I was only able to find the file with the information of my saved wlan connections (WTF, why are the passkeys writting in clear text, not crypted in any way??) - this was the only file in the /data/misc/wlan directory.
I actually only want to full wipe as a last consequence,
since my phone's a bit shaky. Last year I had a severe issue with my sd-card slot (maybe someone remembers), which somehow disappeared month later without any interaction - pure magic. I even replaced the slot before with no improvement - suddenly the functionality returned.
I actually don't want to lose sd-card functionality again, so i even fear flashing a new rom.
I hope there is someone who can give me some input - maybe some config files are missing or stuff - i only hope its not hardware related.
In the meantime I also tried reflashing my rom and flashing the radio again,
no success
EDIT:
Okay screw it, I wiped and flashed my rom again - same issues,
Sounds like a hardware issue...
any ideas?
Greetings
HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.
Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app