Database Develop

[Q] for 4.1.2 root, what is the difference between build no.?

Hi,
I want to root my device, which i have upgraded recently to 4.1.2
the thing is, I found some information in root threads regarding build no. like XXAMA1, XXAMA2, XXAMA4 ...etc
what are the differences between them? if all of them are 4.1.2 JB?! will anyone work?
to make it easier, which thread can work to root my SG3mini device:
Android version: 4.1.2
Baseband version: I8190XXAMA3
Kernel version: 3.0.31-860525
Build number: JZ054K.I8190XXAMA3

You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.

tys0n said:
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
Click to expand...
Click to collapse
can you root with a 4.1.1 custom version on a 4.1.2?

TerenceTP7 said:
can you root with a 4.1.1 custom version on a 4.1.2?
Click to expand...
Click to collapse
Yes you can, but only if you make a factory reset first. Otherwise you'll have bootloops or force closed apps.

tys0n said:
Yes you can, but only if you make a factory reset first. Otherwise you'll have bootloops or force closed apps.
Click to expand...
Click to collapse
now i have a official firmware 4.1.2 ,baseband I8190XXAMA2.before this i had a rooted 4.1.1 by avicoh.but my phone didnt boot anymore,so i flashed with the official 4.1.2 and after that with PARAM.
so now i need to factory reset,but the one that i now have isnt the one that came with my phone from the store.doesnt it give any problems when i factory reset?
original from the store was 4.1.1 JB

TerenceTP7 said:
now i have a official firmware 4.1.2 ,baseband I8190XXAMA2.before this i had a rooted 4.1.1 by avicoh.but my phone didnt boot anymore,so i flashed with the official 4.1.2 and after that with PARAM.
so now i need to factory reset,but the one that i now have isnt the one that came with my phone from the store.doesnt it give any problems when i factory reset?
original from the store was 4.1.1 JB
Click to expand...
Click to collapse
No it shouldn't be any problem. Factory reset makes sure there is no leftovers from previous install. Clears cache, settings, user data.

tys0n said:
No it shouldn't be any problem. Factory reset makes sure there is no leftovers from previous install. Clears cache, settings, user data.
Click to expand...
Click to collapse
alright,i trust you on this.i did the reset my phone rebooted and now its stuck on the bootlogo(galaxys3mini gt-i8190).do i need to wait?or?
..
..
still stuck on bootlogo after 10minutes.doesnt look good.use param again?
---------- Post added at 06:04 PM ---------- Previous post was at 05:40 PM ----------
ok,that didnt work..man im getting headache of this..
i booted my phone again using PARAM.
do you know a root version for my phone?maybe a version that clear all my data too?
---------- Post added at 06:28 PM ---------- Previous post was at 06:04 PM ----------
TerenceTP7 said:
alright,i trust you on this.i did the reset my phone rebooted and now its stuck on the bootlogo(galaxys3mini gt-i8190).do i need to wait?or?
..
..
still stuck on bootlogo after 10minutes.doesnt look good.use param again?
---------- Post added at 06:04 PM ---------- Previous post was at 05:40 PM ----------
ok,that didnt work..man im getting headache of this..
i booted my phone again using PARAM.
do you know a root version for my phone?maybe a version that clear all my data too?
Click to expand...
Click to collapse
the one that you have http://forum.xda-developers.com/showthread.php?t=2178346 is this a root version?for the netherlands?can i use it on my phone?

Just flash a wipe.tar and then your firmware.
I never had to flash param.lfs to get it boot.
Once I had to pull the battery and power on again when it got stuck on boot after flash.

tys0n said:
Just flash a wipe.tar and then your firmware.
I never had to flash param.lfs to get it boot.
Once I had to pull the battery and power on again when it got stuck on boot after flash.
Click to expand...
Click to collapse
i did used it once that wipe.tar but get stuck on bootscreen.
do you need to wait long on bootscreen while flashing with wipe.tar?
and how does it work?just odin>pda,select wipe.tar>start?

TerenceTP7 said:
i did used it once that wipe.tar but get stuck on bootscreen.
do you need to wait long on bootscreen while flashing with wipe.tar?
and how does it work?just odin>pda,select wipe.tar>start?
Click to expand...
Click to collapse
Yes flash as pda. It's basicly the same as a factory reset.
If your phone reboots after, just put it in download again and flash firmware.

tys0n said:
Yes flash as pda. It's basicly the same as a factory reset.
If your phone reboots after, just put it in download again and flash firmware.
Click to expand...
Click to collapse
and what if its get stuck on bootscreen again.use PARAM?

TerenceTP7 said:
and what if its get stuck on bootscreen again.use PARAM?
Click to expand...
Click to collapse
Afaik the param.lfs is mostly just a bunch of pictures. Don't know what it does, except loads the phone with startup/downloadmode pictures.
http://forum.xda-developers.com/showthread.php?t=1750645
http://z4ziggy.wordpress.com/2010/09/18/looking-into-param-lfs-file/

tys0n said:
Afaik the param.lfs is mostly just a bunch of pictures. Don't know what it does, except loads the phone with startup/downloadmode pictures.
http://forum.xda-developers.com/showthread.php?t=1750645
http://z4ziggy.wordpress.com/2010/09/18/looking-into-param-lfs-file/
Click to expand...
Click to collapse
i dont get it.i have my 4.1.2 rooted now,but after flashing ,my phone doesnt boot.it only boots when i flash the PARAM file.i restarded my phone to check if that works and that works fine.i dont think this is a big problem,is it?
at first sight everything works fine.
WIPE doesnt work,and factory reset doesnt work either.is there a option to do this manually.i have clear master,is that the same?

tys0n said:
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
Click to expand...
Click to collapse
thank you tys0n for your replies! i kept my CSC, didn't change it.. since i'm already having 4.1.2 (last firmware for s3 mini till now)
and followed this way to root my device:
http://forum.xda-developers.com/showthread.php?t=2150979
and it worked
the only thing is, this way increased the flash counter! i dont know how is this bad, but i guess just if i want to give it to someone to check it, they will know, right?!
BUT I found other rooted ROM that they will reset binary count after flash to "none"! and will show firmware as "official" instead of "custom"..
anyway, good to learn and i'm saying all that just in case any noob like me saw this thread in the future maybe they can find one useful info or two
sorry TerenceTP7 that i can't help you.. still new to those things..
and thank you again tys0n

Sv: [Q] for 4.1.2 root, what is the difference between build no.?
Search triangle away here on xda. It's an app that will reset your binary count to zero
Sent through time and space from my s3mini.

BRICKED? Stuck in bootloop?

Alright, so I ****ed up to the max
I wanted to install cyanogen mod, i unlocked the bootloader, and installed twrp, i then attempted to root because twrp was not able to backup or wipe, but i then realized that android was stuck in bootloop.
For some really stupid reason i decided to relock the bootloader.
So now, I have twrp that cant do anything, a locked bootloader, and a non working android rom, and i cant unlock the bootloader again because of the checkmark in developer options that I cannot get to because i cant even load it.
Someone please help

arbitercu said:
Alright, so I ****ed up to the max
I wanted to install cyanogen mod, i unlocked the bootloader, and installed twrp, i then attempted to root because twrp was not able to backup or wipe, but i then realized that android was stuck in bootloop.
For some really stupid reason i decided to relock the bootloader.
So now, I have twrp that cant do anything, a locked bootloader, and a non working android rom, and i cant unlock the bootloader again because of the checkmark in developer options that I cannot get to because i cant even load it.
Someone please help
Click to expand...
Click to collapse
Ouch. I think you may be stuck. @rootSU is there anything else possible?
---------- Post added at 07:02 PM ---------- Previous post was at 06:53 PM ----------
You can try to fastboot format userdata and cache but I doubt that will even work.

Evolution_Freak said:
Ouch. I think you may be stuck. @rootSU is there anything else possible?
---------- Post added at 07:02 PM ---------- Previous post was at 06:53 PM ----------
You can try to fastboot format userdata and cache but I doubt that will even work.
Click to expand...
Click to collapse
So i found a post on how to fix it, So now what i have is a bootlooped recovery, with an unlocked bootloader, making progress
EDIT: pushed cyanogenmod, got it to boot up, but i'm scared that it will happen again

arbitercu said:
So i found a post on how to fix it, So now what i have is a bootlooped recovery, with an unlocked bootloader, making progress
EDIT: pushed cyanogenmod, got it to boot up, but i'm scared that it will happen again
Click to expand...
Click to collapse
Congratulations!! At least you don't have a brick. Do not re-lock your bootloader and you'll be OK.
---------- Post added at 08:43 PM ---------- Previous post was at 08:09 PM ----------
You should really share what you did for the benefit of others though.

Evolution_Freak said:
Congratulations!! At least you don't have a brick. Do not re-lock your bootloader and you'll be OK.
---------- Post added at 08:43 PM ---------- Previous post was at 08:09 PM ----------
You should really share what you did for the benefit of others though.
Click to expand...
Click to collapse
Yes, and let us all count this as a victory for the users of these forums.
I don't know why this makes me want to high five this guy, but I am stoked to hear about this.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 08:52 PM ---------- Previous post was at 08:49 PM ----------
arbitercu said:
So i found a post on how to fix it, So now what i have is a bootlooped recovery, with an unlocked bootloader, making progress
EDIT: pushed cyanogenmod, got it to boot up, but i'm scared that it will happen again
Click to expand...
Click to collapse
Congratulations, and let it be known that the CyanogenMod rom you're flashing is unofficial, and nearly every dev on these forums whom builds from CM source has likely done exactly that which resides in that thread, only personally, so as to familiarize themselves with what is in the pipeline.
Is it great to have it? Yeah. Is it the work of DHacker? Nope.
Sent from my Nexus 6 using Tapatalk

arbitercu said:
So i found a post on how to fix it, So now what i have is a bootlooped recovery, with an unlocked bootloader, making progress
EDIT: pushed cyanogenmod, got it to boot up, but i'm scared that it will happen again
Click to expand...
Click to collapse
I forgot to unlock oem and my bootloader is locked. But I can't boot up to anrdoid.
Sounds like the same issue.
How did you fix?

I used the above mentioned tactics, just keep clearing cache and user data, and other things until you get signs of recovery working or android

Stock boot.img..

Close thread please.. Thank you.

Hi
beachbum40 said:
I'v been looking for the stock boot.img for this build. Has someone pulled this boot.img yet..thanks
Click to expand...
Click to collapse
I've got nexus 6 and the problem is that is STATUS CODE 2 and I can't unlock bootloader again.
But again I can't entar the system eather it says Android is starting,optimizing 1of126 and restart... Does it have solution for this or not?

beachbum40 said:
I'v been looking for the stock boot.img for this build. Has someone pulled this boot.img yet..thanks?
Click to expand...
Click to collapse
Just extract the stock rom with 7-zip and you'll see the different IMG files, including boot.img.
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
VladimirX3M said:
I've got nexus 6 and the problem is that is STATUS CODE 2 and I can't unlock bootloader again.
But again I can't entar the system eather it says Android is starting,optimizing 1of126 and restart... Does it have solution for this or not?
Click to expand...
Click to collapse
Boot into recovery and data factory reset.

gee2012 said:
Just extract the stock rom with 7-zip and you'll see the different IMG files, including boot.img.
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
Boot into recovery and data factory reset.
Click to expand...
Click to collapse
I have to apologize to everyone for this not so smart post.? I had a few drinks in me and obviously wasn't thinking clearly.. ?
Before anybody says anything "no I'm not a drunk" lol. I just happened to have a few glasses of wine to many. I'm seriously a lightweight.. Anyway after my head cleared up I realized what to do. I've been an Android enthusiast for some time now and its rare that I ask for help.
I really appreciate the suggestions though and will be asking for this post to be removed..
I also appreciate you all not flaming me as well?

ASUS MeMO Pad 7 ‏(ME176CX)‏ Not updating to lollipop

As it says in the title. How to i get it to install. My Tablet is rooted.

Updating this tab to lollipop isn't a good idea (lots of bugs) but have a look here: http://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965

Saarge said:
Updating this tab to lollipop isn't a good idea (lots of bugs) but have a look here: http://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965
Click to expand...
Click to collapse
I had seen that but it didnt work at all.

Dublin2275 said:
I had seen that but it didnt work at all.
Click to expand...
Click to collapse
If you have a ww sku try to put this file (http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip) on the root of you microSD card and reboot the tab, it should try to flash it (well not on first reboot, you'll have a notification asking you if you want to do the update); if this doesn't work either try the nandroid (https://www.androidfilehost.com/?fid=24052804347832070) from jerbear, it was done on an unmodified me176c with lollipop, you must use the tethered recovery, make a backup, reboot, replace your back up files by the files of the nandroid, then reuse the tethered recovery and restore from the new back up. Ask jerbear from this forum for further explanation, i'm just a user who had the same problem, not a specialist.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Ps; the system will do an update after the nandroid restore, it is an older version of the me176c's lollipop rom.

Saarge said:
If you have a ww sku try to put this file (http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip) on the root of you microSD card and reboot the tab, it should try to flash it (well not on first reboot, you'll have a notification asking you if you want to do the update); if this doesn't work either try the nandroid (https://www.androidfilehost.com/?fid=24052804347832070) from jerbear, it was done on an unmodified me176c with lollipop, you must use the tethered recovery, make a backup, reboot, replace your back up files by the files of the nandroid, then reuse the tethered recovery and restore from the new back up. Ask jerbear from this forum for further explanation, i'm just a user who had the same problem, not a specialist.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Ps; the system will do an update after the nandroid restore, it is an older version of the me176c's lollipop rom.
Click to expand...
Click to collapse
I have the ME176CX not the ME176C i think that has something to do with it

Dublin2275 said:
I have the ME176CX not the ME176C i think that has something to do with it
Click to expand...
Click to collapse
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.

Saarge said:
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Click to expand...
Click to collapse
Does that update mess up the current root i have? Will i need to do a fresh install?

Saarge said:
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Click to expand...
Click to collapse
And also if i do a factory reset will i still have the update or can i get it all the way back?

Dublin2275 said:
Does that update mess up the current root i have? Will i need to do a fresh install?
Click to expand...
Click to collapse
You'll have to root again indeed, but remember what i said in the start, you're likely to regret it if you manage to do the update, it's a very bugged one.
---------- Post added at 09:51 AM ---------- Previous post was at 09:44 AM ----------
Dublin2275 said:
And also if i do a factory reset will i still have the update or can i get it all the way back?
Click to expand...
Click to collapse
a factory reset doesn't give you the original rom, the update will still be there, the downgrade is a very tricky process, and i answered you only because you asked, but i repeat myself, you should really keep your tab the way it is now, i regretted having done the update for months until someone finally found a way to roll-back to kitkat.
With lollipop you'll have:
-memory leak (can be fixed anyway).
-overheating.
-crashes.
-apps closing themselves or refusing to launch.
-random reboots of the tab itself.
-some users even had clock issues on the tab (too slow).
-others had battery life issue (tablet discharging too fast).
---------- Post added at 09:56 AM ---------- Previous post was at 09:51 AM ----------
oh and i forgot, google apps crashs.

Reset After Every Reboot

Every time I reboot my phone, it resets to factory settings and I see the "Welcome" screen. It only does this when the time in TWRP is inaccurate (e.g. 10:03AM when it's 8:49PM). I've reinstalled twrp, reinstalled the ROM, locked and unlocked the bootloader, but nothing works. I just get the same blue screen.

I actually have the exact same issue

Anyone? (bump)

thats a strange issue you on custom rom? i dont have this device but i ordered it and this post getting me worried

captain here i had the same issue this morning when i tryed to reboot to add some mods on Octos Rom it's a bug in force encryption i really want my data to be secured and encrypted but at the same time it makes it hard to play with.
Solution : flash stock recovery then factory reset the phone
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
nitinvaid said:
thats a strange issue you on custom rom? i dont have this device but i ordered it and this post getting me worried
Click to expand...
Click to collapse
u should be worried this new encryption thing is awesome for normal users but it will make it hard for the devs

Do you have f2fs or extv4 partition? f2fs is currently having some issue..better to stay with extv4 for some time

venomus001 said:
captain here i had the same issue this morning when i tryed to reboot to add some mods on Octos Rom it's a bug in force encryption i really want my data to be secured and encrypted but at the same time it makes it hard to play with.
Solution : flash stock recovery then factory reset the phone
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
u should be worried this new encryption thing is awesome for normal users but it will make it hard for the devs
Click to expand...
Click to collapse
i was using nexus bcoz of development and bought one plus becouse of development
is there any way to avoid it?

nitinvaid said:
i was using nexus bcoz of development and bought one plus becouse of development
is there any way to avoid it?
Click to expand...
Click to collapse
It worths every penny keep it on rooted stable stock in my opinion

Unbrick Tutorial
OK, so far I've used this unbrick tutorial to get me completely back to stock (version 3.5.1) and now I'm waiting for the OxygenOS to finish the OTA. Will report back when finished.

venomus001 said:
It worths every penny keep it on rooted stable stock in my opinion
Click to expand...
Click to collapse
i am a theme developer so i cant use stock

nitinvaid said:
i am a theme developer so i cant use stock
Click to expand...
Click to collapse
Then u ll have to disable encryption so u can use whatever rom u like without bugs

venomus001 said:
Then u ll have to disable encryption so u can use whatever rom u like without bugs
Click to expand...
Click to collapse
How to disable encryption? need bootloader or a kernel??

Still no luck. Does anyone know why the time is off by several hours in TWRP?

nitinvaid said:
How to disable encryption? need bootloader or a kernel??
Click to expand...
Click to collapse
use OnePlus3T-ToolKit-v2.0 to disable it
also don't use PIN lock on ur rom
---------- Post added at 01:28 AM ---------- Previous post was at 01:05 AM ----------
RockCityGeek said:
Still no luck. Does anyone know why the time is off by several hours in TWRP?
Click to expand...
Click to collapse
did u try flashing the stock recovery if no then u need an other way to clean data partition as sed it's and encryption problem
1- download OnePlus3T-ToolKit-v2.0
2- connect ur device in fastboot
3- choose flash stock recovery
4- flash stock recovery and wait for it to boot
Note : if u dont want to lose ur data try flashing TWRP 3.0.4 insted

[delete]

[delete]