yashsingh1/xdaforums huggingface dataset:
[Android] toolstone:
may be i can but after my exams..

I can give u lollifox rom if u want.. i ported it but i'm getting nvram error..
[Android] waseemmayaa:
please give me link if you have uploaded it I'll try otherwise I'll return to pussyfap :P

---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------

whats nvram error i am newbie please tell me if you can...? but i want to give a try to lollifox, sounds good lollifox...!
[Android] toolstone:
U can't connect to wi-fi.. But u can fix it..
[Android] waseemmayaa:
Give me link of that rom lollifox rom and how can i fix wifi issue...? Tell me procedure.... I will try...!
[Android] toolstone:
lollifox.zip - https://drive.google.com/file/d/0BxD_-w8z-qhlc3JpdnlobEJKaFE/edit?usp=docslist_api

Copy nvram folder from your device to sdcard before flushing rom..
[Android] waseemmayaa:
where is nvram folder in my device and what to do next after copying that folder to sdcard....?
[Android] himanshu honor holly:
On screen buttons

How can i get on screen buttons on tihs roms
[Android] toolstone:
Screen bottons.. why..?
[Android] himanshu honor holly:
Navigation bar is easy ,faster and i like it too :p
[Android] toolstone:
Ok go in build.prop of find this line "qemu.hw.mainkeys = 1" without "" if it is 1 make it 0 if it is 0 make it 1 and then reboot

..
[Android] waseemmayaa:
Thank you [MENTION=6533193]toolstone[/MENTION] I also tried this and its working....! See screenshot....!
[Android] waseemmayaa:
[MENTION=6533193]toolstone[/MENTION] after installing lollifox my both sims not working help please
[Android] toolstone:
Use sp flash tool and flash the rom.. root it and restore our backup rom..
[Android] waseemmayaa:
i have tried all the roms but not solved
[Android] toolstone:
U flash our rom b105 by sp tool method..
[Android] waseemmayaa:
where is the link

---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------

i dont know how to use sp flash tool....? please help me now step by step i have already downloaded b105
[Android] toolstone:
--Install the USB Drivers If they are not already installed on your PC.

---Extract out all the files of SP flash too, and double-click on Flash_Tool.exe to open it.

---Click On the scatter loading button and select the “Scatter File” that you just downloaded. -----The real name of the file is “MT6582_Android_scatter_emmc.txt”.

---Check the all items are clicked.

--and Press download button.

--Pull out the device’s battery, and while it’s turned off connect it to your computer via USB cable.

-- after connecting press volume up key..

--And download started.

--when you see Green color tick mark then Disconnect the mobile.

Lets Switch On the mobile.

Or see this..

http://www.micromaxunite2.net/2014/09/how-to-flashrestore-stock-rom.html?m=1
[Android] waseemmayaa:
Please someone solve th8s error system ui force stopped application stopped itself....?
[Android] ebiraaam:
i m flash rom

but no boot :(
[Android] aman283:
Battery Sucker

bad rom
[Android] SunnyTee:
well?

Any bugs?
[Android] waseemmayaa:
(y)
[Android] Yallamandareddy:
Some Bugs

1) On dailer call button not not visible

2)In Security Pattern not visible.
[Android] Ferizal79:
Key guard is bug, ui system sometimes appears to have stopped, please give a solution, because I love this ***** rom
[Galaxy Note 4 Q&A, Help & Troubleshooting] magichoward:
I've noticed that Google is syncing my photos despite the fact that I chose in settings only when plugged in .any one else having this issue.

I reinstlled the app and battery went back to normal.
[Mi 3 Android Development] Bitti09:
[CENTER]/*
* Your warranty is not void - from Xiaomi.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
[/CENTER]

Changes to stock TWRP:

All usefull commits from omnirom Gerrit are included in this Build (New default Theme for example)

Download:

Mirror 1: Androidfilehost

Mirror 2: XDA Dev Db Downloads

Last Build Date: 06.06.2015

Changelog

: https://github.com/CM-Cancro/android_bootable_recovery/commits/cm-12.1

Note about Updates:

Don't ask for "

next build ETA

" or "

Updates

" for this recovery build !!!

I'll check omnirom source every friday and if there are new commits a new build will come online within 48h

XDA:DevDB Information

Unofficial TWRP with cherries, Tool/Utility for the Xiaomi Mi 3

Contributors

Bitti09

Source Code: https://github.com/CM-Cancro/android_bootable_recovery

Version Information

Status: Stable

Created 2015-06-07

Last Updated 2015-06-07
[Mi 3 Android Development] miss:
how intalacion?
[Mi 3 Android Development] marko94:
Just flash with fastboot or with this app link
[Mi 3 Android Development] miss:
Flahs y Ahora hay Enciende el telefono, siemrpe vuelve al recuperación.

recuperación Otro instalo y Es Como si no lo hiciera, vuelve al recuperación de bity

---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------

Lights flash and now the phone, siemrpe back to recovery.

install another recovery and it's like it does not, return to the recovery of bity
[Mi 3 Android Development] Skar3:
Any bugs in this recovery? It's possible to flash with CWM?
[Mi 3 Android Development] marko94:
No bugs, works perfectly ! don't know for cwm, if can't flash trough fastboot or via app
[Mi 3 Android Development] HidekiRyuga:
Does it work for mi4?
[Mi 3 Android Development] purval6300:
thank u sir, any info about dual boot... or we have to use it for system 1 only
[Mi 3 Android Development] iTalisman:
I think it can be flashed through TWRP as well. We'll have to use the .img option.
[Mi 3 Android Development] JanalTom:
Work fine in my MI4

flash zip in attachements ...

BACKUP BEFORE FLASH ...

CREDITS: Bitti09

Tested on my MI4 ...
[Mi 3 Android Development] Skar3:
Racconended this instead of CWM?
[Mi 3 Android Development] marko94:
Yes,of course:D
[Mi 3 Android Development] Skar3:
Installed, thank you Bitti09! nice theme :)
[Mi 3 Android Development] Tomi_Ohl:
There's a problem with the latest version... When trying to restore system, it writes that system is read only... This didn't happen in the previous version by Bitti.
[Mi 3 Android Development] marko94:
Just try reboot few times in recovery, and allow modification ..it works for me
[Mi 3 Android Development] Gopinath15:
Can some one provide screenshots. I already have TWRP v2.8.6.0

Fashed this img file. I dont see any difference :)

Where can I find whether my recov is Bitti's :)
[Mi 3 Android Development] Tomi_Ohl:
This happened 2/2 times... Which modifications should I enable?
[Mi 3 Android Development] Skar3:
What modification?

Here is some screenshot :)
[Mi 3 Android Development] marko94:
this
[Mi 3 Android Development] Gopinath15:
ahh... poor me. I was using the themes and dint knew that my theme has changed

Mine was looking like the attached screenshot. Deleted UI.zip now

Cool. Thanks guyz
[Mi 3 Android Development] Tomi_Ohl:
Hmm thanks.

Now I'll search where is an option for this. I didn't have a popup like this.
[Mi 3 Android Development] Skar3:
You mean this?

In italian is read only
[Mi 3 Android Development] Skar3:
any news on the update?
[Mi 3 Android Development] Bitti09:
Will check twrp sources and upload a new build if there were changes in a few hours
[Mi 3 Android Development] Bitti09:
recovery-14-06-2015.img will be online in a few minutes.

Changes:

- Rebased source
[Mi 3 Android Development] Skar3:
Anyone tried Last build?
[Mi 3 Android Development] Tomi_Ohl:
Just tried it, working fine as always.

What I like about it, that it doesn't heat up while taking backup :good: (unlike the other one by kundancool).

One thing should be changed: backups are placed in a folder named "167c841". This isn't practical, they should be in a folder called "MI_3W" (like in other recovery).

EDIT: almost forgot: now restoring backups are working.
[Mi 3 Android Development] Bitti09:
New Build Online

+Changes:

- Backup path names are now fixed.

+Download Info:

Filename: recovery-16-06-2015.img

md5: 58b79a7ff687f7a6ae7a3f2c0e0348c7
[Mi 3 Android Development] shabtab:
How to check if I have successfully upgraded it, there's no about option. Using TWRP itself to update..
[Mi 3 Android Development] ej8989:
Flashed this on top of the official twrp. Did a backup, restored it, then rebooted the phone. Everything works!

I can say that this build is more reliable than the official twrp. Very fast and stable. :good:
[Mi 3 Android Development] rajatvohra:
whats in cherry's?

noob question

what does an recovery has to do with cherry's .

plz answer this question as answering to a newbie
[Mi 3 Android Development] ej8989:
Cherry-picks (or cherries) in this thread are carefully selected features from another source and then added to the recovery to distinguish it from stock.

This one:

Changes to stock TWRP:

All usefull commits from omnirom Gerrit are included in this Build (New default Theme for example)
[Mi 3 Android Development] josedb:
I had flashed the 16.06.15 and with rashr , but when boot to recovery it has changed to mi recovery but in asian languages, not english is not shown :S , which alternative to install this do i have? thanks

edit: nevermind, i used flashify and it works
[Mi 3 Android Development] josedb:
https://drive.google.com/file/d/0B5GBvepEuRskOU1PTDJWTTFCejA/view?usp=sharing
[Mi 3 Android Development] ronysingh:
Can Someone Plzz Make a Zip of Latest Img-16-06-2015??

I am Unable to Flash .img file From both Rashr and Flashify,,,, it Again Boots in CWM..!!

Only Zip Can Help Me..!!
[Mi 3 Android Development] ceriqdesign:
See the 1st page bro..

http://xdaforums.com/showthread.php?p=61227102
[Mi 3 Android Development] ronysingh:
Its The Old Version...

I wanted New one..

Antway U can try Official Theme Preview Twrp.zip
[Mi 3 Android Development] ceriqdesign:
[QUOTE=ronysingh;637

yup..its a bit old and its unofficial..
[Galaxy Tab S General] YrrchSebor:
Since I cracked my T700 screen I've been looking around and saw this: http://www.a4c.com/product/samsung-...rvM_ACfXmg-rb6hip782YDOZ-hSizo8QmEaAhiu8P8HAQ

I went all the way to the final step of the purchase but backed out(there was no tax or shipping charges for me!). I might just wait for the Tab S2 but I thought this looked like a decent deal?
[Galaxy Tab S General] Maduro78:
Screen repair is $199 through samsung

sent from my LG G4 vs986
[Fire HD 6 and 7 Original Android Development] jmz:
Everything seems to be working. No known issues. USB-OTG works also

Downloadhttps://www.androidfilehost.com/?fid=24052804347756852

or use our TWRP Manager software to install it automatically for you

Install either by DD or maybe flashify will work for you.

dd if=recovery.img of=/dev/block/mmcblk0p7

Thanks goes to [MENTION=912474]Dees_Troy[/MENTION] as this was my first MediaTek based device to build recovery for

This will also be taken official this week.
[Fire HD 6 and 7 Original Android Development] jmz:
Pulled download temporarily
[Fire HD 6 and 7 Original Android Development] alucard_xs:
Thanks for your work dude but we do not have recovery image for our Fire 6 HD sadly ...
[Fire HD 6 and 7 Original Android Development] jmz:
The HD 7 and HD 6 are EXACTLY the same device. The OTAs for both are EXACTLY the same. The only difference is the screen size. There essentially is no difference betweent the 2 devices
[Fire HD 6 and 7 Original Android Development] alucard_xs:
Sure but what about factory / recovery image, is there anyone floating around ?
[Fire HD 6 and 7 Original Android Development] jmz:
just dump your current recovery.img.

dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img

Then as soon as you boot into recovery make a backup.
[Fire HD 6 and 7 Original Android Development] ryanyz10:
Root

Will flashing the SuperSU package in recovery root, or cause a bootloop?
[Fire HD 6 and 7 Original Android Development] jmz:
Dont need to flash anything with TWRP. If you boot twrp then choose reboot to system option it will ask if you want to install SuperSU.
[Fire HD 6 and 7 Original Android Development] jmz:
Reuploaded fixed version. Found a couple bugs that i didn't notice before. All good now
[Fire HD 6 and 7 Original Android Development] bibikalka:
So for us the slow ones, can you explain this in detail?

You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?

Will Amazon update re-write the recovery partition so you are back to stock ?
[Fire HD 6 and 7 Original Android Development] jmz:
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery
[Fire HD 6 and 7 Original Android Development] bibikalka:
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.

And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? :D How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!! :D

You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):

http://xdaforums.com/fire-hd/help/internal-memory-structure-hidden-t3122246

So even without a custom ROM there are tons of easy tweaks that one could do.

I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).

Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!
[Fire HD 6 and 7 Original Android Development] jmz:
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.

Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.
[Fire HD 6 and 7 Original Android Development] bibikalka:
I just saw your boot unlocker thread, you should better manage your cross-references :D Congrats for getting us this far!

But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?

Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.

Exciting times, man !!!!
[Fire HD 6 and 7 Original Android Development] jmz:
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.

Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.
[Fire HD 6 and 7 Original Android Development] bibikalka:
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?

In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?

(from /recovery/etc ):

#!/system/bin/sh

if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then

log -t recovery "Installing new recovery image"

applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p

else

log -t recovery "Recovery image already installed"

fi
[Fire HD 6 and 7 Original Android Development] jmz:
all devices have that in some form or another.

I would make a dd backup of the stock one before flashing.
[Fire HD 6 and 7 Original Android Development] bibikalka:
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?
[Fire HD 6 and 7 Original Android Development] jmz:
No there isn't.

Well, I guess I am out of the game for awhile. Just bricked my Fire.
[Fire HD 6 and 7 Original Android Development] bibikalka:
That sucks ... What did you do ? Some messing with recovery partition?

Any pointers on how to load Amazon updates via TWRP to get back to updated stock?
[Fire HD 6 and 7 Original Android Development] jmz:
Nah. I was trying to get a custom kernel to boot. I downgrade the bootloader lost recovery somehow. So I can't restore the boot partition.

Yeah it should flash fine from twrp. But you WILL lose root. and if you don't remove the recovery directory in the zip you will lose twrp too. but when rebooting after flashing it should give you the option to install SU.

It formats /system completely.
[Fire HD 6 and 7 Original Android Development] bibikalka:
Success!!!

OK, followed the instructions, got TWRP installed. :D

Python on Windows is a bit rough, I had to figure out how to run it. It needs more packages than posted (cuber.py is missing), had to get the full set of files from here :

http://xdaforums.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689

To run it I did this from the directory with these py files:

C:\Python34\python.exe cublock.py XX YYYYYY

Also, needed to grab fastboot driver, from here:

http://xdaforums.com/fire-hd/general/to-fastboot-t2988597

I just unpacked the exe file, and installed the driver via Windows when prompted upon fastboot, then I could unlock.

TWRP from the store worked beautifully, no issues, quick and efficient. TWRP looks slick (as it always does!!!), I will mess with it a bit more in the next few days. I am a bit unclear about root access after a TWRP ROM flash, will it offer to install "su" ?!?

I may be less ambitious and will install 4.5.3 again, just to see how it goes (and in case recovery gets reset back to stock). After all, we know it's rootable !!! :D
[Fire HD 6 and 7 Original Android Development] jmz:
Yes if it detects no SU package installed it will ask if you want to install it.
[Fire HD 6 and 7 Original Android Development] bibikalka:
I made some progress on how to modify the update files from Amazon in order not to ruin the TWRP, will try to get a few clarifications from the HDX thread:

http://xdaforums.com/showpost.php?p=61244948&postcount=51

But I am thinking that we can get a slightly stripped down Amazon update, and then apply GAPPS via TWRP, and other good things.

While working on this, I found some tasty lines in tz.img (TEE1) and lk.bin (UBOOT) from the update bin:

$strings tz.img

...

[%s] This is a production device.

[%s] Device Unlocked!!! Skip LK verification.

[%s] Verifying LK...

[%s] fail to verify Second Bootloader.

[%s] This is an Engineering device.

[%s] User build Unlocked!!! Skip LK verification.

...

$strings lk.bin

...

Device or user build unlocked, or non user build on engineering device! Skip kernel verification.

%s androidboot.unlocked_kernel=true

Verifying kernel with engineering key...

Verifying kernel...

%s androidboot.unlocked_kernel=false

...

Anyway, I have no idea if such info can be of any use.

With 20.4.5.1 update out there, we can go back in time to the buggiest versions of UBOOT and TEE1, which should hopefully increase options for successfully booting a custom kernel.
[Fire HD 6 and 7 Original Android Development] bibikalka:
If I understand correctly, you flashed UBOOT partition with some older version from the updates, and it stopped booting TWRP ? People on HDX forum were flashing their aboot right and left, I wonder why in your case the older UBOOT did not work ... Perhaps, you have to unlock it again as per instructions if you want to get your unsigned TWRP to boot? You should be able to get at least into fastboot if your UBOOT is working at least a little bit ...

It seems that the sequence for the boot is UBOOT, then recovery, so unlocked UBOOT can boot unsigned recovery (and you could boot unsigned boot.img from recovery partition).

For the regular boot, UBOOT (LK) boots boot.img, If LK does not have to be signed now (since UBOOT is unlocked), can the regular LK be simply patched to set androidboot.unlocked_kernel=true just in case (which it seems to be able to do) ? I do "getprop" on my supposedly unlocked fire, and I get "ro.boot.unlocked_kernel=false"

I also wonder what is the function of TEE2 partition, Amazon never updates it. Is this a thing for MTK chipset ?
[Fire HD 6 and 7 Original Android Development] freddy_rv:
Hello guys, [MENTION=6680544]bibikalka[/MENTION]

I am stuck in the recovery and can't go any further. Is there a way to install TWRP to restore the fire hd with factory image?

Thanks in advance.
[Fire HD 6 and 7 Original Android Development] junglistknot:
So excited to see some ROMs in the future. Great work and thanks for the tutorial.
[Fire HD 6 and 7 Original Android Development] junglistknot:
Success I was finally able to unlock the bootloader and install twrp onto my HD 7. Now I just wait for a cool custom rom.
[Fire HD 6 and 7 Original Android Development] bibikalka:
I've retraced these steps with the same results.

1) Flashing 4.5.3 bootloader of top of unlocked 4.5.3 - still unlocked

2) Flashing 4.5.1 bootloader on top of unlocked 4.5.3 - still unlocked

3) Flashing a modified kernel with the unlocked 4.5.1 bootloader - it does not boot, and the buttons to go to recovery do not work (vol+ and power) !!! Brick. I am working on un-bricking it via the US Postal service ;)

Some idiotic programmers did not add an option to 4.5.1 bootloader to go into recovery by pushing buttons. In hindsight, I should have checked if 4.5.1 bootloader allows recovery via the buttons.

My next test is to use MTK flashing tools and try to revive the brick. If the MTK tools work, that would be game over - flash anything and everything without issues. Will report on how this last test goes.

Update The sweetspot is 4.5.3 bootloader. Nothing else is good. I've rooted 4.5.2, and installed TWRP, and again, it does not let you get into recovery via the button pushes. But since the system was OK, I could reboot into recovery via adb commands. So before anything, always update the bootloader to version 4.5.3 first in order to be able to get into bootloader via the button pushes.
[Fire HD 6 and 7 Original Android Development] cmm324:
So, I attempted to the upgrade to 5.2 listed in this forum while going back to stock recovery and maintaining root. I have found, that I cannot get the adb sideload to work with twrp, it crashes everytime. First time, it corrupted /system, I was able to reformat it, but any other time I try to install anything via zip or adb sideload to system, it dies. adb sideload to boot works fine.

I still have TWRP, but no OS. Debating attempting to flash stock recovery... scared.

Update: I was able to 'install' the 4.5.4 package that was prepped for TWRP. I will have to figure out what he did to the bin to make it work.
[Fire HD 6 and 7 Original Android Development] Krsmqn:
Still available?

Is twrp still available for these devices?
[Fire HD 6 and 7 Original Android Development] DoLooper:
Sure. Download at post #2
[Fire HD 6 and 7 Original Android Development] jrob09BHS:
Getting permission denied from direct link and app won't download the img file. Can you make the download public?