Database Develop

[Q] Bootloop, help, newbie

So, I have a nook color and I installed roms in it, rooted and other basic things. But recently my girlfriend got a dell streak from his brother and from two weeks of use, today it bootloops every single time. I have no experience on how to install the recovery or roms in it. My girlfriends brother never rooted it or changed the stock firmware. This is the device information I copied when I first took the device:
OS:
HC 3.2
Base band:
11.810.09.06.00
Core (kernel?) version:
2.6.36.3
OEM version:
GLUNB1A151130
Build:
19921
Service tag:
BH2L2P1
So, can I just factory reset (user data and internal tablet storage) the device and flash (software upgrade via update.pkg on sd card) the 21700 build on this page (http://forum.xda-developers.com/wiki/Dell_Streak_7#Official), or I have to do something else first?
Thank you very much in advance.
Update:
The factory reset solved the bootloop, now I am reading the posts to see which costume rom to install. Do you recommend one for battery life, performance and/or stability? Stock Froyo, Costume Froyo, Stock HC (version 511), update to version 514 of Stock HC, Costume HC (HoneyStreak R8 or other), CM10 nightlies?
Also, I know that the tab haves a sim slot, but I don't know which tab version is (4g, 3g or other). The original owner threw the box away long time ago and doesn't remember anything about the tab specifications. Is there a way to know which version is the tab with an app or a terminal command?
Thanks.

Well, you're the 1st person that I've seen have 511 firsthand.
Would you be willing to make a dump of it before updating?
As you're the 1st, you'll likely be the last with it.
As far as boot loops are concerned, if you have not rooted and modified system files: a fac reset should fix it.
If you/someone did modify files, that's likely the reason.
It's possible it's the rom itself that's the issue (or the hardware, we'll assume it's not a hardware issue unless otherwise), but noone else can comment as it's not a common version.

TheManii said:
Well, you're the 1st person that I've seen have 511 firsthand.
Would you be willing to make a dump of it before updating?
As you're the 1st, you'll likely be the last with it.
As far as boot loops are concerned, if you have not rooted and modified system files: a fac reset should fix it.
If you/someone did modify files, that's likely the reason.
It's possible it's the rom itself that's the issue (or the hardware, we'll assume it's not a hardware issue unless otherwise), but noone else can comment as it's not a common version.
Click to expand...
Click to collapse
I am not that tech savy, but I am guessing you want a "copy" of the rom for future references or development. Sure, no problem.
How do I do that? I have found this link (http://www.freaktab.com/showthread.php?401-Dumping-ROM-using-ADB-guide). Is it a complete guide or do you have a best guide/link to do it with this device?
Also, I updated the first post, managed to get out of the boot loops with the factory reset now that I am at my own home with this baby. XD
Wanted to update it tomorrow at first hour but first I would do the dump.
Thanks.

[Q] Dell S10 Pro - Need help in Updating
Read that and repeat the steps, it's essentially the same thing.
Requires that you understand the command line (just basic commands)
The major differences: (on the S7 instead of the S10)
APX mode is Vol up + vol down + power
Use this bootloader: bootloader.bin
Files of interest: P4, P5, P9, P10, P11
Any needed files are listed in stickies on the dev subforum, if you need more specific instructions, just ask.
(except for basic "how to use the command line", there are many tutorials on the web)
Beyond that, to update, just download the 514-30 version from the wiki, the one with a baseband version indicated.
As you seem to have a US4g model, that would be the one to use.
(assuming you wish to use a stock rom)

Since you have a DS10, Honeystreak nor CM10 will work on it.
As I don't have one, I haven't made a ROM for it.

He has a S7, I merely linked to that thread as I just helped someone do the exact same thing on a S10.
Steps are more or less identical as it uses APX mode, with the differences already mentioned.

Ah gotcha.
Sent from my Nexus 7 using Tapatalk 2

Are the partition image files available somewhere for download ?

TheManii, I've sent you the dropbox link in your inbox, please check if everything is alright.
Sorry for the extended delay... :s

Assuming that dump you gave me is a good image: I would recommend updating to 514 first regardless of what you're ultimately going to flash.
You'll have a good baseline to compare incase you wish to flash a custom rom afterwards.
As you have a stock recovery (assuming you didnt overwrite it with a custom one), just download the 514-30 us4g pkg and update.
I dont know if a manual update will wipe data, so you would be recommended to make a backup beforehand
Edit: the dump seems to be good (in that it doesnt look corrupt offhand) thanks

To backup I have to install the costume recovery of one of your threads ([Recovery]Clockwork Mod 6.0.1.2: http://forum.xda-developers.com/showthread.php?t=1334487) or is it a better way to do it (NVflash or other recovery)?
I would normally only update, but since this 511 version is uncommon, who knows if somebody else needs it in the future for something in particular.

If you're backing up userdata, use a custom recovery.
You can use "fastboot boot <image name>" instead of "fastboot flash recovery <image name>" to only run it instead of permenently installing it.
511 is only important because I collect roms, beyond that it's not terribly interesting.

Pic of Dead Droid with ! after firmware update attempt

I recently got my TF701T back from repairs and they of course factory reset it (they put a new battery in). We all know it needs factory reset for that right? Anyways. I do a check for updates and nothing. I know I was running 4.4 previously but updater says no updates and stuck on original. So I start reading and download the latest US 4.4 firmware directly from ASUS, unzip it and put in main directory (verified mine was US) and reboot. Says all is fine, would I like to update, yes, reboot and I get the Android gear guy for about 10 minutes then it reboots. He shows up again and dead android shows up.
Now it just loops forever to this. I spent about 5 hours reading forums here, attempted a restore, but 1. the recovery.img link is bad and 2. my tablet isn't rooted.
Any suggestions? I can access the fastboot screen that gives me "RCK, Android and "Wipe Data". I tried Wipe data 3 times, no good still getting dead guy. I tried copying the latestest zip file to an sd card with boot.img and blob and file and ran RCK and it says match then reboots then dead guy again...
the fastboot screen says "released by: "US_epad-10.14.1.45-20131014" which I believe is the original.

You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!

So, I had downloaded 3 different versions multiple times before with zero success. But, once I took one and renamed it to T4_SDUPDATE.zip bam!
You just so made my day!
Thank you! Thank you! Thank you!
Devan

I have a question along these lines. What is the difference between the software update and firmware update and when do you do each? I understand the difference between what they are I suppose just not sure if updating is the same. Should I update kernel too or is that updated in an SW or FW update?
Thanks

Anyone?

I have seen these terms used very differently on different device forums.
Here on the Asus tablet forums people mostly talk about firmware when they mean the whole stock package. The stock firmware always comes with everything: Bootloader, recovery, rom and kernel
On the HTC M8 forum for example, they make a clear distinction: Software is rom and kernel, firmware is bootloader, radios, baseband etc.
The recovery seems to fall somewhere in between
Your bootloader version determines everything else. You should only flash a recovery, kernel or rom compatible with that particular bootloader.
You can, or have to, update it if you want to run a rom that requires a later or newer bootloader. Asus encrypts their BLs, so bootloader updates can only come from them - so far only with the release of a new version of the OEM "firmware".
If you as an unlocked, custom rom'd user then want to install a rom based on that new firmware, you have to update the bootloader and possibly but not necessarily your recovery before flashing the new custom rom.
Custom recoveries get more frequent updates. CWM, TWRP or some enterprising dev release new versions every few months. Always make sure it is compatible with your bootloader and rom. In most cases you can easily skip a few versions. But if you update your rom, let's say, from JB to Lollipop you should also update your recovery.
The kernel is considered to be part of the rom. At least every rom I know of comes with a kernel, some even with several to choose from. And it is a popular sport to try the same rom with different kernels.
You update the rom whenever the developer releases a new, updated version - or not if you're happy with what you got.
The safest place to be is always up-to-date: The latest roms usually require the latest bootloader and it's best to run both with the latest recovery.
If you have a working combo you can stick with it for years if you like.
But if you've been away for a while, did not follow the latest development, and want to update, you always have to:
Check if your bootloader is still current. If not, update it
Update your recovery
Wipe data, cache and Dalvik
Flash the new rom.

Nice explanation, I knew all of this but there is no way I could have explained it.

berndblb said:
You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!
Click to expand...
Click to collapse
THANK YOU!!!! IT worked like a miracle... Thank you !!!! :good::good::good:

[Q] Return XT1095 to Stock?

Hi All---
I'm an old-time flashaholic who hasn't flashed in a long time.
However, I'm so sick of the memory bug, that I'm going to try out CM12 on my xt1095.
However, I want to verify that there is a way to later return my phone to stock so that I can recieve the OTA when the fix (eventually) comes.
I can't find a thread that tells me how to do it (on the old moto x you would use an sbf, but i don't see anything about that around here.)
Thanks so much for your help in advance...

1 Making a backup in recovery of your actual stock rom and restoring when needed (with twrp for example)
2 Flash via bootloader with fastboot official rom (no zip to flash)
3 using RsdLite using official rom (no zip to flash)
Cheers
Ps: ota is another thing already discussed here

michyall said:
1 Making a backup in recovery of your actual stock rom and restoring when needed (with twrp for example)
2 Flash via bootloader with fastboot official rom (no zip to flash)
3 using RsdLite using official rom (no zip to flash)
Cheers
Ps: ota is another thing already discussed here
Click to expand...
Click to collapse
Any clue where I'd find the official ROM (either for fastboot flashing or rsdlite)? I can't find any links...
My phone is already on 5.0, fwiw.
Thanks for the help

There is a lot of topic about stock roms on this forum, in your settings you have to search what version do you have (see picture) and download that one.
But i don't kno if you're expertor maybe you know what you are going to do. I ask you: twrp installed? Rooted? Why not doing a backup without downloading tons of mb and going crazy flashig 10 files?
That's my opinion.
Last word, search this forum, there is a lot of discussion like this one

Forgot screenshot

I don't have the link but the XT1095 retail/tmobile 5.0 full image can be directly downloaded from Motorola just like the images for the Moto X 2013.

N00B question from an old-timer

I have a Galaxy Tab s2 (810) and am currently running 5.1.1 (optimalROM R1-1 DEODEX) and I'm stumped.
I've been flashing ROMs on Androids for years. Always the process is:
Root the device
Install new boot loader (Currently TWRP)
Download the zip file for the ROM and GAPPS onto my Mac.
Copy the files to the external SD
Reboot Galaxy into TWRP
Factory reset
Flash new ROM and GAPPS
Reboot.
Subsequent flashings don't require the first two steps.
I want to try MM so I looked on the forum, and downloaded one of the CyanogenMod 13 betas. After flashing, I got caught in a boot loop, so I restored my backup. Then I read the flashing instructions more carefully, and learned that I must revert to the "Factory" version of MM before I can flash CM 13.
Here are my questions:
Won't that put me back at square 1? have to re-root and install TWRP again?
Where can I get the correct version of the "Factory" rom? The download sites I've found are all kind of sleazy looking pay-for-download sites.
Is there even a version available in English? All of the options seem to be European or far-east countries.
It looks like a utility called ODIN is required, but it appears to be a Windows executable. What do I do on the Mac?
WHY is all this nonsense necessary in the first place? I've never encountered anything like it in literally hundreds of download/flash experiences. I did have to repartition the memory on my Xoom, but there was a separate utility to do that.
Thanks for the help
Walt

walts said:
I have a Galaxy Tab s2 (810) and am currently running 5.1.1 (optimalROM R1-1 DEODEX) and I'm stumped.
I've been flashing ROMs on Androids for years. Always the process is:
Root the device
Install new boot loader (Currently TWRP)
Download the zip file for the ROM and GAPPS onto my Mac.
Copy the files to the external SD
Reboot Galaxy into TWRP
Factory reset
Flash new ROM and GAPPS
Reboot.
Subsequent flashings don't require the first two steps.
I want to try MM so I looked on the forum, and downloaded one of the CyanogenMod 13 betas. After flashing, I got caught in a boot loop, so I restored my backup. Then I read the flashing instructions more carefully, and learned that I must revert to the "Factory" version of MM before I can flash CM 13.
Here are my questions:
Won't that put me back at square 1? have to re-root and install TWRP again?
Where can I get the correct version of the "Factory" rom? The download sites I've found are all kind of sleazy looking pay-for-download sites.
Is there even a version available in English? All of the options seem to be European or far-east countries.
It looks like a utility called ODIN is required, but it appears to be a Windows executable. What do I do on the Mac?
WHY is all this nonsense necessary in the first place? I've never encountered anything like it in literally hundreds of download/flash experiences. I did have to repartition the memory on my Xoom, but there was a separate utility to do that.
Thanks for the help
Walt
Click to expand...
Click to collapse
i can answer a few of your questions:
you can try this http://techbeasts.com/download-odin-jdoin3-mac/ odin for mac, not tried it myself though or you could try running odin via WINE on your mac
you can get the latest firmware/software from https://samsung-firmware.org/model/SM-T810/ you can sign up for a free account and it takes a few hours to download the firmware though!
install that via odin and you will be back to factory settings

Why don't you just flash the stock mm firmware?
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

Why don't you just flash the stock mm firmware?
Click to expand...
Click to collapse
See my questions above. I was hoping to not have to start all over again as if I had just bought a new galaxy. I've never encountered this kind of situation with any other device. Usually a "Factory Reset" followed by flashing the CM ROM is adequate. I'm guessing there is something unique about the hardware design that requires all these contortions.
Walt

walts said:
See my questions above. I was hoping to not have to start all over again as if I had just bought a new galaxy. I've never encountered this kind of situation with any other device. Usually a "Factory Reset" followed by flashing the CM ROM is adequate. I'm guessing there is something unique about the hardware design that requires all these contortions.
Walt
Click to expand...
Click to collapse
You won't lose anything by updating to mm.
Your data, apps, settings and everything else will be as they were previously.
The firmware only updates the OS and doesn't wipe anything.

walts said:
See my questions above. I was hoping to not have to start all over again as if I had just bought a new galaxy. I've never encountered this kind of situation with any other device. Usually a "Factory Reset" followed by flashing the CM ROM is adequate. I'm guessing there is something unique about the hardware design that requires all these contortions.
Walt
Click to expand...
Click to collapse
I believe it has something to do with resizing the partitions (or adding an extra one), so that's why you have to update to stock Marshmallow.

TWRP-Installation went badly wrong....

Hello Guys!
My device:
Redmi Note 9 Pro (European)
Bootloader-Status: Unlocked ✓
Root-Status: rooted ✓
Recovery-System: doesnt work x
Fastboot-Mode: does work ✓
As described above i stupidly flashed the wrong TWRP version to my device. Now i end up in a bootloop with the error code "System has been destroyed" and i can't get into the system anymore. Another big problem is that the device can't detected/recognized anymore by any console using adb and the Mi-Flash-Tool also can't see it as well ...
Does anyone have any solution or ideas for my problem? I bought the phone recently and don't have enough money to buy another ...
I would even pay money for the solution.
Someone said i have to flash the stock partitions back again. But which tool/method allows it me to flash the stock partitions back again? I have no idea how to flash ANYTHING without using adb or recovery mode ...
Thank You In Advance

"System Has Been Destroyed" means only three possibilities:
Partition SUPER has been modified,
Partition VBMETA has been modified,
or Partition CUST has been modified.
Just flash the stock partitions back again, but from the same version already present on the device.

VD171 said:
"System Has Been Destroyed" means only three possibilities:
Partition SUPER has been modified,
Partition VBMETA has been modified,
or Partition CUST has been modified.
wefawefdcwea
Just flash the stock partitions back again, but from the same version already present on the device.
Click to expand...
Click to collapse
ok thank you very much so far! I can see it's not possible to flash stock partitions using adb. can you tell me which tool or method i have to use to flash the stock partitions back again?

You can't flash partitions using adb.
Try spflashtool.

So was busy the whole day finding a solution.
My goals so far:
-installing spflashtool
-installing drivers for spflshtool
However i don't find any site where to download/buy stock partitions for redmi phones ...
Can you suggest a source for them? Are custom firmware's and custom ROM's the same ?
Have a nice day!

{Mod edit: Quoted post has been deleted}
I spent almost the last day watching videos on youtube on it and i wouldn't post something here if i had found someting....
Can You at least please tell me - Are custom firmware's and custom ROM's the same ?

All steps for spflashtool are same for all devices.
Keep trying.

Can You at least please tell me - Are custom firmware's and custom ROM's the same ?
Thats all in have to know....

you simply have to reflash your stock firmware again, Google your device firmware and phone Model, or search your model on androidhost.ru and flash using something like team mt multitool