[Q] [S.O.S.] A rare MILESTONE brick situation! - Motorola Droid and Milestone Q&A, Help & Troublesh

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

Related

[Q] rooting nexus one

hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System

[Q] Installing ICS from CM7.2?

Hi,
Sorry if this seems like a dumb question - A bit confused from reading up all the info on upgrading to ICS on the p990.
Im running a volk custom kernel, and CM 7.2 - OS Version 2.3.7.
Whats the "best" way to upgrade to the new ICS? I tried running the LG software update but it doesnt go too well, fails after it tries to detect phone - even though it detects it initially.
Can I get the release that LG released with my setup?
Please advise.
Thanks!
Same situation here. I'm on official cm7.2 and would like to upgrade to ics. But don't think that useing official lg update tool is so good idea - it might brick your phone. It won't update to ics because you aren't running the official GB rom so lg update tool won't upgrade (correct me if i'm wrong).
Maybe the AIO tool would do the trick.
Anyways, people we need your advice!
LOL, use NVflash ICS rom like TG.
for me the best way is using the toolkit to install new partition, new bootloader and recovery
than boot into recovery and flash the room as usual
Thanks Wakata.
Much appreciated. I have tried downloading the toolkit but its always corrupt.. ill download the 7 zip format.
I take it that I will need to back everything up and wipe everything, install new partition, boot loadder and recovery(CWM??), then flash with the new rom and kernel?
I've also used the All-In-One P990-Toolkit to upgrade to ICS.
You can use 1. to backup your internal SD in case you need it later.
Then hit 4. to change the partition layout and after that 8. to flash the new unlocked bootloader. That's all.
Thanks again
Slight problem - I downloaded the 7z file, and extracted them, but cant seem to run the .cmd file? What am i doing wrong here?
scratch that last question.. for some reason the files are corrupt when i download them.. grrrr.
So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please
Nevermind, I had a fiddle and flashed ics 6.0.xxx.. lets see how it goes. Hopefully I havent bricked it lol
Sorry, problem.
I first tried option 1, then 4, then 8.. after its all done, no errors - I boot the phone, and its stuck on the red LG logo.. I've left it there for around 10-15 mins with no luck? Help!
Haha, actually I figured it out. I did realise I didnt have a ROM! Doh! lol rookie mistake.
I downloaded this rom and kernel(1.4ghz OC) and its running pretty well, no bugs so far(touch wood)

[Q] only boots into recovery

ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.

Help a newbie; LG Optimus L90; learning to flash

Current situation: pretty much complete newbie. I broke my factory OS after rooting it, I think I deleted something Settings needs, so anytime it needs to access settings I get "Unfortunately, Settings has stopped." I factory reset it hoping that would help, but now after loading it gets stuck on a cycling white screen reporting that error (I think it's trying to set up the phone.) The error message prevents me from doing the touch-four-screen-corners trick I've read about and bypass set up. So, stuck on phone setup errors as near as I can tell.
I do have my user apps backed up with TiBu, but couldn't get the recovery zip from TiBu to work. I downloaded CWM but didn't figure it out yet. Also unfortunately I can't get the USB drivers to work (the LGE Android MTP Device won't install), so I think my only way of getting files to my phone now is using the microSD cards.
I'd love some help! I think my factory OS is FUBAR, so I'm not trying to fix that, instead I'd rather just get a cool ROM loaded so I can continue learning with a working device with said cool ROM. I don't fully understand terms that I know I need to like "bootloader" or what CWM / TWRP actually does or how to use them (I need to make a custom recovery ROM?). Or where to get a cool ROM or which to pick, some step by step basics on from some experienced users would be fantastic! Thank you so much!
So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...
lfom said:
So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...
Click to expand...
Click to collapse
Thank you, this put me in the right direction. I ended up discovering that even though the " LGE Android MTP Device won't install," the flashing process worked with this program via USB anyway. I'm going to lick my wounds a bit before trying to flash a custom ROM. Thank you!
For the rom installation, after unlocking your bootloader and rooting, download the app Flashify from Google Play, then install TWRP or CWM zip file as recovery image. Then, from there, you can install custom ROMs or make backups of your phone, etc. A cool custom ROM I recommend is CyanogenMod, it ports newer versions for older devices. So, you can have Android 6.0.1 in your phone

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.

Categories

Resources