Develop Bugs

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] Broken NEXUS7 upgrade help!!!

I have quite a special case here....The story goes...
I bought a NEXUS7 2013 like two years ago and rooted it with Teamwin.
A few month later, I dropped it while charging and broke the MicroUSB Input and wasnt able to charge it. That was not a huge problem because I bought a wireless charger. The only problem was: I couldnt connect it to the computer. And teamwin was still running in the background.
Now that android lollipop has arrived, I tried to update the system.
But because of teamwin, It refused to happen. I tried a few times and ANOTHER threat appeared. Android wouldnt let me download the system update anymore. It said: Insufficient space to download. I had like 3Gb left???
{
"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 think there was a way to flash Lolipop whithout connecting the tablet to a pc, but that would Erace all the data I have in this tablet. Since I cannot connect it to a pc AND do not have a memoryStick plot, The only thing I can do is to upload everything on drive or something, but that would take a hell of a lot of time.....
Pls help me! I really want lollipop!
Goal: System update WITH teamwin installed, WITHOUT erasing the data and WITHOUT connecting to a pc.
Problem: MicroUSB input BROKEN
My Tablet: NEXUS7 2013, Android 4.4.2( I had teamwin since then, couldnt update it.), ROOTED!
THANKYOU!! Oh and I am quite the bigginer, so pls explain every step!

Hi there,
Please wait until mods will move this thread to the device specific forum.
Stand by

kaikai21321 said:
I have quite a special case here....The story goes...
I bought a NEXUS7 2013 like two years ago and rooted it with Teamwin.
A few month later, I dropped it while charging and broke the MicroUSB Input and wasnt able to charge it. That was not a huge problem because I bought a wireless charger. The only problem was: I couldnt connect it to the computer. And teamwin was still running in the background.
Now that android lollipop has arrived, I tried to update the system.
But because of teamwin, It refused to happen. I tried a few times and ANOTHER threat appeared. Android wouldnt let me download the system update anymore. It said: Insufficient space to download. I had like 3Gb left???
I think there was a way to flash Lolipop whithout connecting the tablet to a pc, but that would Erace all the data I have in this tablet. Since I cannot connect it to a pc AND do not have a memoryStick plot, The only thing I can do is to upload everything on drive or something, but that would take a hell of a lot of time.....
Pls help me! I really want lollipop!
Goal: System update WITH teamwin installed, WITHOUT erasing the data and WITHOUT connecting to a pc.
Problem: MicroUSB input BROKEN
My Tablet: NEXUS7 2013, Android 4.4.2( I had teamwin since then, couldnt update it.), ROOTED!
THANKYOU!! Oh and I am quite the bigginer, so pls explain every step!
Click to expand...
Click to collapse
If you want to stay on stock, I'm not sure there's an easy answer since you cannot connect to a PC.
But if you're already rooted and using a custom recovery, you can follow these steps to flash any custom ROM (there may be a stock zip floating around here somewhere, cleanrom and AOSP grogg's way will also both be close to a stock experience).
1. First, back up all the data you care about in case something goes wrong
2. Update your recovery - download the latest TWRP (teamwin) recovery image to your device (http://techerrata.com/browse/twrp2/flo), then flash the image to your recovery partition. I recommend using the Flashify app from the Playstore. Once it's installed and opened, click to flash a recovery image, select the recovery .img file, and confirm, then reboot (reboot to recovery if you want to confirm the flash was successful).
3. Download a ROM zip you want to flash, and the appropriate Gapps package if needed (and maybe the latest SuperSU zip for good measure, for gaining root if the rom you flash does not have root access built-in). You can find all of this by searching the forums here.
4. Reboot to recovery.
(4.1. - make a nandroid backup in TWRP)
5. Wipe everything but internal storage (system, cache, dalvik, and data).
6. Flash ROM (as well as SuperSU zip and Gapps if needed).
7. Reboot, be patient, first boot may take awhile on lollipop
8. Profit!

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.

Question Phone rebooting Kernel Framework crash and DM verity error

Hi,
I have a 6 month old EU model of this phone which has started rebooting frequently and displaying a DM Verity Corruption Error, the MUI Ui log folder shows abnormal reboot kernel /framework.
{
"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"
}
This phone is running stock software and has never altered / unlocked / rooted.
I've tried factory reset from within the settings menu and restoring backup, I've also tried wipe and reset from the recovery menu and not using my backup or installing anything and it still rebooted after 35mins up time, the device is not hot not has it been dropped.
I've also tried reinstalling the latest firmware but could only get this to work from within the setting and selecting download latest package.
I tried to download the latest recovery firmware and copy to SD CARD, naming as update.zip and it did not try to flash when I used the recovery boot (power off and power on holding power and volume), I also tried from the settings, about phone, MIUI press it a lot and then under the dots choose select package but it tells me it's not allowed to install an unofficial package.
I've tried to contact customer service and had the 'thank you we will respond in 48 hours', I think something may have been corrupted on the last MIUI update and it's very annoying as it's my Wife's phone and my Poco X3 NFC has been brilliant.
I can't seem to find other way to try and clean install the software, please can anyone relate to these issues and offer some advice on how I may be able to flash the current software over itself , of course it could be a hardware fault but it seems too much of a coincidence it is since updates have been received.

damianiw said:
Hi,
I have a 6 month old EU model of this phone which has started rebooting frequently and displaying a DM Verity Corruption Error, the MUI Ui log folder shows abnormal reboot kernel /framework.
View attachment 5887881
View attachment 5887879
View attachment 5887883
This phone is running stock software and has never altered / unlocked / rooted.
I've tried factory reset from within the settings menu and restoring backup, I've also tried wipe and reset from the recovery menu and not using my backup or installing anything and it still rebooted after 35mins up time, the device is not hot not has it been dropped.
I've also tried reinstalling the latest firmware but could only get this to work from within the setting and selecting download latest package.
I tried to download the latest recovery firmware and copy to SD CARD, naming as update.zip and it did not try to flash when I used the recovery boot (power off and power on holding power and volume), I also tried from the settings, about phone, MIUI press it a lot and then under the dots choose select package but it tells me it's not allowed to install an unofficial package.
I've tried to contact customer service and had the 'thank you we will respond in 48 hours', I think something may have been corrupted on the last MIUI update and it's very annoying as it's my Wife's phone and my Poco X3 NFC has been brilliant.
I can't seem to find other way to try and clean install the software, please can anyone relate to these issues and offer some advice on how I may be able to flash the current software over itself , of course it could be a hardware fault but it seems too much of a coincidence it is since updates have been received.
Click to expand...
Click to collapse
Bootloader locked check.if yes try to flash MIUI 13.0.6 full firmware 3gb size .it will be fixed or try to reinstall firmware with mi flash tool and locked bootloader