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.
Related
Please let me start out by saying that I have two epics and a tab, all sprint. I read and post and donate regularly on the Epic4g forums. I'm not a newb, just someone that is trying to get the most out of his devices.
I have read about 70+ pages over multiple threads including the bible and other stickies, spent several if not tens of hours...and I have to say I'm just lost enough to need to post this.
Please no slams, just help and post your answer, or click to another thread and ignore. Thanks in advance.
1. Trying to get Ext4. It looks like Ext4 is *maybe* doable if you try using a verizon tab flash somewhere, but I dont see enough replies to make me comfortable enough that it works. I have a class10 SD card, similar to what I have in my epic that is all ext4. Any advice ?
2. Trying to apply OTA for Sprint - I am on DJ29 baseband and DJ30 build. Cant get the OTA to work, it goes about 11seconds into the install and then I get triangle with an exclamation next to Mr Android. Reboots automatically, update doesnt apply. I *am* rooted, with z4root. I already went to stock using Privacy, but didnt flash anything.
3. Recovery. So...no CWM for Sprint ? Rom Manager isnt the same thing.....and doesnt have an option for Sprint tab anyways. What is working for the sprint tab?
4. Flashing. Im used to Odin, saw Heimdall (never used that), and dont see any recovery working here for Sprint...so stopped there just in case. Also seen reference to SGS. What is recommended for Sprint users.
5 After I get Ext4 and OTA, would like to try a good combo of Kernel and Rom, preferably overclockable. This is different than the Epic in that there, we just do Rom, and Firmware doesnt seem to be much of an issue - everyone just uses a base of the DK28 hack release or the stock release. Seems there are more firmwares here, mostly not for Sprint.
And to answer the top of the thread poll about *REALLY* liking the idea of a Sprint only subforum....OMFG yes. That would really make a lot of this easier......
Thanks again for the help.....I appreciate it guys.
anyone ? )))
Im also in need of sprint tab help as well, i heard voodoo say that conversion was successful after flashing this http://forum.xda-developers.com/showthread.php?t=941781
however wouldnt boot and got stuck at the Samsung screen (boot loop)
since then i flashed this:
KhasMek.Voodoo.plus.CDMA.Tab.v2.zImage
and this together
KhasMek.DJ11.KleanMod.v2.ext4
still stuck at samsung, and now voodoo says "not enough space on partition" "system not available"
EDIT: i flashed back to sprint stock and all good
EDIT: i flashed KhasMek.Voodoo.plus.CDMA.Tab.v2.zImage again and still getting stuck at samsung after successful voodoo conversion.
Been stuck at the logo for ever think it has something to do with that hidden partition that tries to reinstall all your old apps -_-
This is exactly why I sold my sprint tab and got the t mobile tab. Just not enough support.
Someone got CWM to work on a sprint tab. You will just have to read the thread for that portion.
Good luck w/ getting what you need. It is tough to get stuff for the sprint tab.
jkurl said:
This is exactly why I sold my sprint tab and got the t mobile tab. Just not enough support.
Someone got CWM to work on a sprint tab. You will just have to read the thread for that portion.
Good luck w/ getting what you need. It is tough to get stuff for the sprint tab.
Click to expand...
Click to collapse
Agreed, but now that i got flashing back to rooted stock figured out its a breeze to flash and try stuff, albieit there's not much to flash
Which Sprint stock did u use?? link plz
Okay, you guys that want the ext4 conversion for sprint, why don't you try this, get heimdall all set up, download koush's zImage (last I checked it was a bad link in his thread so I've mirrored it HERE) and perform this command
Code:
heimdall flash --recovery verizon_zImage --kernel verizon_zImage
that should convert you over to ext4 safely and allow you to boot into your system (note, my K-lean ROM probably won't work on sprint tabs, I haven't confirmed myself though). If you can't boot, it will allow you into ROM manager where you can try a factory reset and that should allow you to boot. If you can't convert to ext4 (system giving an error about free space) you should flash the stock kernel via that same method (both --recovery and --kernel) and factory reset. Then flash koush's kernel the way I mention above.
Then, you can safely flash my kernel, but be sure at this point I'm only recommending people to flash via --kernel with my kernel, not --recovery too. This is because my recovery is still not 100% (or even 50%) functional atm (soon, gawds I hope I fix it soon!) and it's nice to have something to fall back on when you need to clear the cache or factory reset. This also causes my kernel to have some issues with the conversion process, which is why sometimes it leaves people at the samsung screen after it claims to have converted properly.
Should be in general
http://forum.xda-developers.com/showpost.php?p=10058503&postcount=1
Boushh said:
Okay, you guys that want the ext4 conversion for sprint, why don't you try this, get heimdall all set up, download koush's zImage (last I checked it was a bad link in his thread so I've mirrored it HERE) and perform this command
Code:
heimdall flash --recovery verizon_zImage --kernel verizon_zImage
that should convert you over to ext4 safely and allow you to boot into your system (note, my K-lean ROM probably won't work on sprint tabs, I haven't confirmed myself though). If you can't boot, it will allow you into ROM manager where you can try a factory reset and that should allow you to boot. If you can't convert to ext4 (system giving an error about free space) you should flash the stock kernel via that same method (both --recovery and --kernel) and factory reset. Then flash koush's kernel the way I mention above.
Then, you can safely flash my kernel, but be sure at this point I'm only recommending people to flash via --kernel with my kernel, not --recovery too. This is because my recovery is still not 100% (or even 50%) functional atm (soon, gawds I hope I fix it soon!) and it's nice to have something to fall back on when you need to clear the cache or factory reset. This also causes my kernel to have some issues with the conversion process, which is why sometimes it leaves people at the samsung screen after it claims to have converted properly.
Click to expand...
Click to collapse
yeah that was a dead end before i think, I'll try what you've suggested, thanks!, right now im getting over 2200 quadrant with stock kernel and zepher Rom and OCLF .. pretty pleased with the results so far, but really want to try your kernel. thanks for your reply
buhler
deathscyte said:
Which Sprint stock did u use?? link plz
Click to expand...
Click to collapse
this has everything you need to flash sprint galaxy tab to stock...
Code:
http://www.ndsico.com/XDA/TAB/Sprint_DJ30_TAB.zip
except the usb drivers which you can find easily.
(just keep in mind that i was setup with the driver Hiemdall uses and had to rollback my driver to the android usb driver to use with Odin. maybe that was just my setup, i dunno..)
EDIT: that link comes from here
Code:
http://forum.xda-developers.com/showthread.php?t=919986
buhlerbuhler said:
yeah that was a dead end before i think, I'll try what you've suggested, thanks!, right now im getting over 2200 quadrant with stock kernel and zepher Rom and OCLF .. pretty pleased with the results so far, but really want to try your kernel. thanks for your reply
buhler
Click to expand...
Click to collapse
Don't flash my kernel with OCLF enabled, OCLF breaks a lot and doesn't produce accurate benchmark tests.
buhlerbuhler said:
this has everything you need to flash sprint galaxy tab to stock...
Code:
http://www.ndsico.com/XDA/TAB/Sprint_DJ30_TAB.zip
except the usb drivers which you can find easily.
(just keep in mind that i was setup with the driver Hiemdall uses and had to rollback my driver to the android usb driver to use with Odin. maybe that was just my setup, i dunno..)
EDIT: that link comes from here
Code:
http://forum.xda-developers.com/showthread.php?t=919986
Click to expand...
Click to collapse
My Tab wont boot still -_-, Im seeing alot of crap in logcat when its trying to boot up, like old appz and games is there anyway to clear that folder, maybe something in there is stopping me from booting?
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.
some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...
Sir, I have tried so, somehow, I did not have lucks other had.
roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
..... my bad
I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me
skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.
By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.
same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App
guys same problem here, help us
Hi there folks!
Im getting mighty confused about this flashing thing.
Im looking to change my ROM to something else then the ICS from Samsung.
Here is the deal.
I read the warning posts and it say (what i think it means) that my build "XLP9" ICS 4.0.3 from Samsung is not safe to do anything on.
I look around on the net to see if there is a way (despite what i read here).
It looks promising.
But all the things i find is ether a lower version of Android (like 2.3.x) or someone is telling me about tons of stuff to download and do before.
So this is were i ask you all.
Do (been searching for 2 days, perhaps my search terms are bad) anyone know if there is a working way to for me to change my version to AOKP for e.g without destroying my phone?
Like i said before, my Build is: XLP9, android version 4.0.3 (from Samsungs update service).
Phone is rooted using CWM.
Its a Note version for the .EU market bought like a few weeks ago (came with 2.3.x i believe).
If you know a thread that contains step by step instructions that will allow me to change the rom, please post it to me here.
Or if I´m screwed for updating to ICS just tell me so to
Cheers
Honken
Hello again.
Yet another day and cant locate any information that im after.
So i tought perhaps there is a way to downgrade the phone back to the factory settings (not ICS).
But since i did the upgrade to ICS is the old rom still on the phone?
I mean to reset it back (same as thode recovery discs on a computer).
Any help or points in the right direction is helpfull at this time.
cheers
Honken
honken08 said:
Hi there folks!
Im getting mighty confused about this flashing thing.
Im looking to change my ROM to something else then the ICS from Samsung.
Here is the deal.
I read the warning posts and it say (what i think it means) that my build "XLP9" ICS 4.0.3 from Samsung is not safe to do anything on.
I look around on the net to see if there is a way (despite what i read here).
It looks promising.
But all the things i find is ether a lower version of Android (like 2.3.x) or someone is telling me about tons of stuff to download and do before.
So this is were i ask you all.
Do (been searching for 2 days, perhaps my search terms are bad) anyone know if there is a working way to for me to change my version to AOKP for e.g without destroying my phone?
Like i said before, my Build is: XLP9, android version 4.0.3 (from Samsungs update service).
Phone is rooted using CWM.
Its a Note version for the .EU market bought like a few weeks ago (came with 2.3.x i believe).
If you know a thread that contains step by step instructions that will allow me to change the rom, please post it to me here.
Or if I´m screwed for updating to ICS just tell me so to
Cheers
Honken
Click to expand...
Click to collapse
It have too many method to change from stock rom to custom rom or aokp. My suggestion is choose your favourite rom and read carefully with the installation method provided at op, then you be fine.
Sent from my GT-N7000 using xda premium
honken08 said:
Hello again.
Yet another day and cant locate any information that im after.
So i tought perhaps there is a way to downgrade the phone back to the factory settings (not ICS).
But since i did the upgrade to ICS is the old rom still on the phone?
I mean to reset it back (same as thode recovery discs on a computer).
Any help or points in the right direction is helpfull at this time.
cheers
Honken
Click to expand...
Click to collapse
Now that you have upgraded to ICS. Those are the factory settings.
Easiest way to downgrade to GB Is by flashing a stock GB rom via pc Odin.
Most of the new ICS custom ROMs now just require you to install AbyssKernel 4.2, then select advanced options and select reboot recovery. Then you wipe your device (wipe data, cache and dalvik cache). From this moment you're free to flash. It all takes less then a minute if you hurry (joking, don't rush when flashing your phone), and it's not very complicated. Do it once and you'll know it's simple.
You need to have a root access first. Plenty of guides how to do it out there.
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.