Develop Bugs

[Q]Bricked Desire...big time

Hello, I tried today to s-off my desire but failed so i gave up but ended up with the usb-brick issue, no problems here, lots of tutorials, but I accidentally updated my phone OTA from HTC and now I don't have amon-ra recovery anymore, only the android recovery which needs signed packages. I do have the SU app installed, so I guess my phone is still rooted, but I am unable to install a recovery in order to unbrick my phone. The only thing that is working is "fastboot", but can't flash a new rom, can't flash a new recovery.
Any ideas? I really don't want to sent my phone to a service...
LE: If I try to install any app from any source, including Market, my phone restarts, fast restarts actually...

tried unrevoked? this installs clockwork recovery mod.
or android flasher -attched

doesnt your phone needs to be ON with unrevoked? from there you must plug it in whith unrevoked opened on your PC.
But you can always try. I highly doubt your phone is unfixable, itll be allright.

Tried to re-root my phone but because my usb connection doesn't work anymore, the unrevoked program doesn't "see" my phone. The only thing that i need, in my opinion is an root explorer packed as a signed zip that the original android recovery can flash and i may be able to regain usb functionality.

you should try a differnt PC and do the process. I had a similar issue sometime back and when I changed the PC i was working on it worked.

That doesn't make much sense because the problem is in my phone, not in my computer...
Latest update: I prepared my phone for service, managed to flash a shipped rom without root, so there is no sign on it that I rooted it or flashed another custom rom/recovery. Still can't access the phone via usb so unrevoked still not a solution. Any new ideas before I say bye-bye to my Desire ?

HyperL said:
That doesn't make much sense because the problem is in my phone, not in my computer...
Latest update: I prepared my phone for service, managed to flash a shipped rom without root, so there is no sign on it that I rooted it or flashed another custom rom/recovery. Still can't access the phone via usb so unrevoked still not a solution. Any new ideas before I say bye-bye to my Desire ?
Click to expand...
Click to collapse
You should try this :
- usb debugging mode ON
- install VWM ( virtual ware machine ) and boot with the .img of the hboot needed at http://alpharev.nl
- the device should be plugged and the aplharev hboot pushed with the last clockworkworld recovery
if not working, unfortunately not so many solutions but you still can try to unbrick the usb and then you will "unrevoked" easily your desire !
Take a look on alpharev developers chat for bricked phones
Hope it helps
My last piece of work
{
"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"
}

Nothing posted on xda or other android forums worked so today I handed my Desire to my carrier because I still have warranty . I hope they don't find any of my modifications , I did un-rooted it so it should be stock enough for them

Something I do not understand :
Last time I USB bricked my phone, I went to hboot, then fastboot, and entered the fastboot commande :
Code:
fastboot oem enableqxdm 0
as stated in many tuto.
This re-enables the USB, and then, you may again flash any recovery via unrevoked.

Actually that command re-enables the micro-sd controller, not the usb.

Worst Case and no more ideas (no rom, no recovery)

Hi!
I just tried to change from RCMixHD (D2EXT) to CM7.
As first, I flashed the AlphaRev CM7 image via Android Flasher and right after that the newest radio version via recovery (32.54.00.32U_5.14.05.17). Since the radio is flashed, i was unable to flash anything in recovery mode, so i decided to format everything, wipe all data so that I just lost my current ROM. It still didn't work, so i decided to reflash the Recovery via Android Flasher and now I can't even boot into the recovery menu. For now I can only boot into the HBOOT and use the fastboot. I got Micro-SD adapter to put anything to my SD-Card, but currently i got no idea what to do. Are there any ROMs i can flash with fastboot?
Got any hints to unbrick the recovery?
Current overview of information:
Desire is S-OFF
No current ROM (full data wipe)
Recovery unbootable (stucks at AlphaRev splashscreen)
HBOOT bootable
SD Card formatted with 5,5gb FAT32 and 2gb EXT4
Got Android SDK installed on my computer

Flash CWM 2.5.0.7 or amon ra via fastboot, make sure it's the desire version and md5 matches. Then install a rom.
Sent from my HTC Desire using XDA Premium App

Or go back to stock with RUU for your phone and start again

Thanks for now!
Just flashed the CWM manually with fastboot and i can boot into the recovery again.
However, the recovery is still hanging up when I do any actions related to the sdcard. No update.zip, no manual chooses possible, no wipe.
But for me, it looks like it's not the sdcard which currently ****s up everything, it seems to be the phone itself. I can still mount my sd in recovery, i can also format everything manually, but as soon as i try to install or choose a factory reset, the recovery ends up in a black screen.
--------
edit:
Okay. Looks like i fixed it now by wiping dalvik, battery stats, cache and then wiping data.
Still confused why it works now, but thank you for pushing me into the right direction. Now i can get everything back to work. Thanks!

why hello there!
Has been a while since i had to recover a phone from a worst case scenario, so i thought i could just revive this thread, as there is no desire 310 subforum yet
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment SP_FT_Dump_05-31-2014-12-45-24.zip
Well. That's it. Thanks in advance for anything that may be posted in here
edit:
pictures mentioned above
{
"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"
}

[Q] Is my Gnex motherboard faulty?

Hi guys,
I can't flash any ROM/Kernel/whatever file via Bootloader/ODIN & Recovery. Worst still I can't access Recovery now.
My Nexus can goto Bootloader or ODIN mode but once i started to push files to it, it will just freeze. Please refer below for photos:
{
"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"
}
BEFORE
AFTER
My Gnex was on the latest Paranoid ROM and Franco kernel.
Timeline:
1. It just went into bootloop when I am just browsing the internet.
2. Went to Recovery to clear cache. (that's my mistake, should have waited longer for my device to boot :crying
3. Still bootloop.
4. Went to recovery to flash stock kernel as I suspect it's kernel fault.
5. Kernel flash failed as it the operation was aborted and restarted. Bootloop again.
6. Done battery pull and went to Recovery to Restore my backup Nandroid.
7. Flashing halfway and it frooze.
8. Can't access Recovery anymore.
9. Tried to restore stock rom using ODIN. Failed at NandWrite as the screen froze as the above image.
10. Tried WugfFresh to restore back to stock rom and failed again as the screen froze.
So guys, can i conclude that my motherboard is the culprit here?
Thanks in advance.

Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?

ual4720 said:
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
Click to expand...
Click to collapse
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:

d3vils said:
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
Click to expand...
Click to collapse
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....

cmaag said:
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
Click to expand...
Click to collapse
corrupt nand partition... that's an interesting theory... will explore on the solutions on the manual fastboot commands...
thanks!!

[Q] Help: Samsung AT&T i747 S3 Soft brick, corrupted os and cant restore.

Hi guys,
I have tried to do a fair amount of reaserch on this topic before posting this thread so i will go ahead and tell you the steps i have taken as to make the helping process as streamline as possible.
Preface:
Can enter Recovery and Download mode - soft brick perhaps. Can start the phone into the OS, Computer recognizes as a removeable device. Able to connect to Odin software.
Problem:
When phone starts and i enter into the rom i get error messages saying google processes stops, media stops, touchwiz home stops. These error messages pop up multiple times. The phone will randomly shut down and display a battery symbol like it is charging (i believe the battery is good since it shows half charged and will increase % the longer i let it charge). I cant really access the SD card from my computer because the phone will force shutdown before i am able to read from the SD athough the computer can detect the SD.
Steps to resolve:
Wipe data and Factory reset in recovery mode
Used odin to install stock firmware. I installed the LK3 AT&T Rom for the I747 from here http://forum.xda-developers.com/showthread.php?p=33570269#post33570269 by extracting it and using Odin to flash the MD5. Sucessfull flash w/o any errors.
Cleared the Cache from recovery after i flashed.
Ideally i want to flash CMW and CM11 on the phone and just be finished with stock rom since it seems like it is causing me a lot of problems. Although it seems like i need a working, function stock rom first to be able to put the needed files on the device and install applications and whatnot before i can do that. What worries me are the random shutdowns even when the phone is plugged in and the corrupt software. Although it still has fully functional recovery and download modes so its not a brick yet.
Any ideas?

If you can get into download mode, you can use Odin to install Philz Touch recovery.
If you have a micro SD card, just copy the rom to the card, put the card in the phone, and use Philz to flash your custom ROM.

audit13 said:
If you can get into download mode, you can use Odin to install Philz Touch recovery.
If you have a micro SD card, just copy the rom to the card, put the card in the phone, and use Philz to flash your custom ROM.
Click to expand...
Click to collapse
I got an (status 7) error when i was trying to flash cm11. Any ideas? It was the proper version of CM.
{
"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"
}

Okay i got the a stable system on the phone now, however . . .
Wifi and Cell networks are not working and i get an error message saying google play services stopped working, i did flash the latest 4.4 gapps and SU.
On bootup i get a message saying,
UIDs on the system are inconsistant, you need to wipe you data partition or your device will be unstable.
How do i fix this?
----------------- Update ------------------
Reflashed the rom and did a full wipe which fixed the UIDs issue. I can also now connect to wifi.
However my phone is still randomly restarting even when it is plugged into my computer. It then turns off the phone and when i press the power button it shows a green battery logo with a circle. What could cause this. I also cannot get the sim card to work, it wont detect any signal.
At this point i have a stable rom installed with the gapps and root and modem.

Check your efs for correct imei, annd which modem are you using, MJB?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Flash protocol/files because of bootloop : soft brick :(

What I've got:
T800 (wifi) updated by mfg. NOT rooted, all is stock (new in 2015 and I've never messed with the OS) and last version was marshmallow 6.0.1 (def marshmallow but version is strictly from memory).
Problem:
Couple of days ago, tab went into endless boot. It would show the android screen then samsung screen then it would load and all looked ok. This would last for maybe 30 seconds then rebooted into the android screen then samsung screen etc. : endless loop.
What I did:
Did some research and booted into recovery mode. Only cleared the cache then rebooted/or shutdown several times. Same looping. Tried cache clear 3-4x with no success. Once I got into the desktop, it lasted ~30 seconds and then booted me out again.
Alright, I bit the bullet and did a factory reset. Well, now it only gives me the android screen and then the samsung screen. Then cycles over again. I cannot get to the desktop anymore, at all.
Found a thread regarding looping but then the threads about upgrading to nougat by @Schischu --> https://forum.xda-developers.com/galaxy-tab-s/development/rom-android-7-nougat-t3449078 then part 2 https://forum.xda-developers.com/galaxy-tab-s/development/rom-t3498956 and then another one by someone else in regards to upgrading past 7.0 (which I'm not ready to do).
The instructions as posted
INSTALLATION INSTRUCTIONS
Cleaning System
This step is only necessary on the initial installation.
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Install this ROM
Go into Install
Flash aosp-XXX.zip
On initial installation it is necessary to Reboot to Recovery. Don't skip this step!
(E:unknown command [log] messages can be ignored.)
Install Google Apps and SuperSU
Go into Install
Flash GAPPS.zip
Flash SuperSU.zip
Reboot to System
Click to expand...
Click to collapse
I've got a few questions as I am a TOTAL newb at this.
1)I've got the following files:
a) aosp_chagallwifi-userdebug-20161116.zip
b) open_gapps-arm-7.0-nano-20191002.zip
c) SuperSU-v2.82-20170528234214-TEST-1.zip
d)twrp_3.0.3-1_sm-t800_10217.tar
Are these the correct files? Do I need any more?
2)when I start the process, do I need to put the ZIP file on an SD card then insert that in the tab?
OR do I unzip the file and put that on the SD card?
OR can I just leave them in a folder (on PC desktop) and access them from there?
3)do I put ALL those files at the same time on the SD card or are they accessed one at a time?
Because I can get the android/samsung splash screen I assume I've still got the correct (ie 6.0) bootloader in place. Correct?
If thats true, then again (q.1): am I ready to start the process?
I figure I should do this to get nougat rather than going through the same procedure to just re-load marshmallow.
Any thing else I should know or have missed?

First some pessimism: when a factory reset doesn't work, it's very likely to be a hardware problem.
But let's assume flashing a new rom can do the trick.
I haven't played around with this tablet, or even another Samsung device, so I'm no expert either, but I think I can guide you a bit.
You'll have to start by installing a custom recovery like TWRP. The one you've found is very old, I would assume that you can find a newer one.
People talk about using a PC program called Odin for flashing recovery, maybe you can search for that. Or read here:
https://wiki.lineageos.org/devices/chagallwifi/install
where they use an equivalent program called Heimdall.

Thanks for the info and link.
Started to look at odin but not having any experience or sure of the files needed, I thought I'd wait and see who might respond.

Interesting times. Was able to find the correct file for odin to use. Appears to be successful but I don't know.
This screen shot is what I got after trying to install gapps.zip
{
"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 says chagall BUT that was b4 I was successful with odin. The error message is the same for Gapps flash. Also, same
error message for SUPERSU
The previously posted instruction said to reboot to recovery. I can only do that if I power down then back to recovery. I do have
an option "reboot to bootloader". Is that the same??

I should mention that I tried the AOSP file (first post) and odin wouldn't accept it. Per instructions I found for odin, the file should end .tar.md5 which I did find
T800XXU1CPK2.tar.md5
Both gave me the same error message though.
+++++++++++++++
I can't install twrp on the tab as its not accepting input so I'm installing android studio on my PC and trying that way.

Well, it must be something else. Although I couldnt load the nougat version with odin, I successfully loaded marshmallow ("PASS" in odin).
https://samfrew.com/download/Galaxy__Tab__S__10.5__-WiFi-__/3klk/XAC/T800XXS1CRI5/T800XAC1CRI5/
BUT I still have the endless boot loop. Plugging in the power cord shuts it off/puts into charging mode.
Do you think it's still a hardware issue?

If you've got an SD card installed, try removing that.
But really, you've reached the end of my knowledge, so let's hope someone else chips in.