Database Develop

[Q] [S.O.S.] A rare MILESTONE brick situation!

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

[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.

(twrp) can't flash rom

So I have a big problem. I wanted to flash a stock 5.0.1 rom so I wiped my device through twrp and when trying to flash, I get an error saying error flashing zip. So now I have no OS installed and cannot use my phone. I cannot connect to my PC so twrp is my only option. I tried download another zip through a PC and copying to sd and get the same error. What can I do?

Managed to flash cm11. (Very good, fast os. Would consider keeping if it wasn't missing key features that make the note 4 like fingerprint scanner and spen.)
So I guess I the other zips might have been faulty? Will reply with updates. Advice would be appreciated.

Either
A) you downloaded the incorrect ROM for your device (910T vs 910T3) or the ROM was meant for a different kernel that wasn't included
B) your download was corrupted. ALWAYS check your MD5 before wiping/proceeding.
Glad you atleast got a functioning phone though... I know how much that sucks

Ok so I'm starting to get really frustrated. Ive tried downloading multiple different zips and keep getting the same error. I don't understand why I cant flash a stock rom >.<

@pavellytime are you trying to flash a stock ROM like lollipop from your carrier? Or a download website?

Can you link us to the site where you downloaded the ROM?
Also what is the model number of 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.

Good start ?

Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.

1stStep said:
Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
Click to expand...
Click to collapse
Hey 1stStep,
A lot off assumptions and questions. And most of them are right.
1. Afaik there are 2 recoveries for the RAZR I. Stock and my build TWRP 3.0.2-0 unofficial. (Thanks for the heads up about the link)
2. Answered in 1.
3. Yep. If your bootloader is unlocked it gives u the function to flash non-stock firmware to the phone. Stock firmware are signed to prevent normal users flashing wrong firmware. Firmware consist of a couple of images. Those images contain data for the partition, just like in your PC. Every image does something else. Most known are boot, data, system, recovery and cache. There are many more. Some needed, some unnecessary.
To answer your question: when u have flashed the TWRP recovery u override the stock one. The TWRP can flash zip files and images to the most known device partitions. From here on u can flash a superuser zip(gives root access on the current ROM/system). Make sure u have the right superuser zip. There are many.
4.
Path to root on stock:
Unlock bootloader->install custom recovery (TWRP)->install superuser zip->reboot and test root on device
Path to custom ROM:
Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like (Gapps(needed for Google playstore and more))->reboot and play with your new ROM.
Off course if u already have the bootloader unlocked and installed a custom recovery, u can skip those.
In the recovery u can also make backups, called nandroid backup. Read up on them and everything u wanna do.
5. The only thing u never want/should do is flashing Android 4.0.4 stock firmware without prior modifications. This is because from 4.0.4 to 4.1.2 there was a change in bootloader (the thing u unlock). If u go back it corrupt a part of the firmware which is difficult to overcome or even impossible without some factory stuff. Everything above 4.1.2 is save. And can always be flashed. The latest stock is 4.4.2 (KIA 20.74) and latest available custom ROM is 4.4.4 (CM11 or soon Lineage 11).
Good luck!

Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again

1stStep said:
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
Click to expand...
Click to collapse
Not at all , just replying if I have some time.
1stStep said:
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
Click to expand...
Click to collapse
- Most custom roms are prerooted.
- Cyanogenmod/LineageOS are prerooted
- Root installed by a zip will not survive any system flashing (rom flashing)
- Any modification to your system partition will not survive and system flashing (rom flashing), though 1 exception:
- installed gapps package (google apps/play store etc.) will survive system flashing on cyanogenmod based roms. But only when updating the rom to a newer version on the same android version. So:
CM11 version 1 to CM11 version 2. (because of a special script in the install zip)
Pre testing a boot or recovery image is blocked on our bootloader. So u can't do it. It's a shame they did it. Working on any boot or recovery changes is a pain in the spoken ass.
If u flash the recovery with:
Code:
fastboot flash recovery recovery.img
there is nothing to be afraid off. The TWRP 3.0.2-0 recovery is well tested on this device.

Thank you again man for all detailed answer.
You're right, it's a shame all these locked things in our phones. I'm sure the guys that agree (our security, blah blah) with these ways to do won't be so happy the day their computers will be locked the same way.
bye bye Hazou.
[Edit] .... hmmm, how long does it take to flash? Yet a 1/4h elapsed and razr still says "Flashing recovery..."
Please, what is the md5 of the image (not the zip, this you give us)? Thanks
[Edit] : Downloaded twice and get md5sum 60dff26f3ee5e9338ee4a6f8cf7df098
but still same forever Flashing recovery ...
[Edit] : I've been puzzled for days being stuck in endless "Flashing recovery ..."
In the ended I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.