FORUMS
Remove All Ads from XDA

 View Poll Results: Did you find this thread useful?

Yes, it was very helpful to me.
 
1,608 Vote(s)
64.01%
No, I didn't feel it helped me.
 
416 Vote(s)
16.56%
I don't know.
 
488 Vote(s)
19.43%

[HELP THREAD] Ask ANY Question. Noob Friendly.

4,429 posts
Thanks Meter: 1,927
 
Post Reply Email Thread
10th December 2018, 02:11 AM |#42491  
scorpio76r's Avatar
Senior Member
Flag All over like street lights
Thanks Meter: 316
 
Donate to Me
More
Quote:
Originally Posted by oeg91

I've read some post about rooting this specific model, but im not sure with one should i follow.
Anyone who have this phone can help me with a guide which you are sure it work with this model? im pretty new at rooting, previus root was using kingroot, which i guess is the simplest way to root, so i dont know much about odin, twrp or flashing.
PS: this one have android 7.0

What's the model?
10th December 2018, 02:37 AM |#42492  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by scorpio76r

What's the model?

j5 prime ms-g5700, build nrd90m.g5700zhu2brh1
10th December 2018, 03:56 AM |#42493  
Quote:
Originally Posted by scorpio76r

What's the model?

They put a title in their post, you can't see it in an app, you gotta view their post in browser to see the title containing their model number. Just a reminder to always look in browser to see if they put a title in their post. Usually, when a user says "this phone" or "my phone" but doesn't post what phone they have, it's because they put a title in their post and they assume that everyone can see it, not realizing that those of us using apps to view the forum can't see the title, they don't know that the title doesn't show in apps.

Sent from my LGL84VL using Tapatalk
The Following 2 Users Say Thank You to Droidriven For This Useful Post: [ View ] Gift Droidriven Ad-Free
10th December 2018, 04:27 AM |#42494  
xunholyx's Avatar
Recognized Contributor
Flag Vancouver
Thanks Meter: 5,060
 
More
Quote:
Originally Posted by scorpio76r

What's the model?

Root for j5 prime sm-g5700
It's in the "title" of the post that you can only see on PC and not in apps.
Although I seldom use apps to go onto XDA, I kinda wish they would get rid of the option for a Title. I've seen it cause confusion quite a bit because a lot of people here are using their phones.
The Following User Says Thank You to xunholyx For This Useful Post: [ View ] Gift xunholyx Ad-Free
10th December 2018, 05:03 AM |#42495  
Junior Member
Thanks Meter: 1
 
More
is there a way that I can decrease the width of the navigation bar on my Galaxy s8+? (I'm looking for a set up like the one on OnePlus devices).
10th December 2018, 08:57 AM |#42496  
Quote:
Originally Posted by Supermutant22

is there a way that I can decrease the width of the navigation bar on my Galaxy s8+? (I'm looking for a set up like the one on OnePlus devices).

Rooted or non-rooted?

Sent from my LGL84VL using Tapatalk
10th December 2018, 02:12 PM |#42497  
scorpio76r's Avatar
Senior Member
Flag All over like street lights
Thanks Meter: 316
 
Donate to Me
More
Quote:
Originally Posted by Droidriven

They put a title in their post, you can't see it in an app, you gotta view their post in browser to see the title containing their model number. Just a reminder to always look in browser to see if they put a title in their post. Usually, when a user says "this phone" or "my phone" but doesn't post what phone they have, it's because they put a title in their post and they assume that everyone can see it, not realizing that those of us using apps to view the forum can't see the title, they don't know that the title doesn't show in apps.

Thank you
The Following User Says Thank You to scorpio76r For This Useful Post: [ View ] Gift scorpio76r Ad-Free
10th December 2018, 05:47 PM |#42498  
carlosalvatore's Avatar
Member
Flag Mexico City
Thanks Meter: 4
 
More
Fiesta IC6
Hi, everybody,

I rooted my Fiesta Duo I6C China phone (Fiesta_I6C_V06_2015_1130) using Kingoroot app. It went well and then I got the brilliant idea of replacing kingoroot's su for SuperSU. I followed this tutorial (Step 6 was what I did) but I got distracted and forgot to install Super SU apk (Step 6.1). I rebooted and the nightmare began. I wasn't able to boot anymore, phone stayed stuck at boot screen.

Then, I made things worse. I decided to clean my mess by performing a factory reset using the built in bootloader (Android System Recovery <3e>).


What happened? well now I have a non booting phone that does not allow adb access because USB debugging is no longer enabled.

I am a linux-only user, with moderated skills, and I am open to suggestions.

fastboot can be initiated, and both phone and computer can see each other.
Code:
$ fastboot devices
0123456789ABCDEF	fastboot
More information about the phone
Code:
$ fastboot getvar all
(bootloader) 	max-download-size: 0x8000000
(bootloader) 	partition-size:userdata: 32000000
(bootloader) 	partition-type:userdata: ext4
(bootloader) 	partition-size:cache: 10000000
(bootloader) 	partition-type:cache: ext4
(bootloader) 	partition-size:system: 60000000
(bootloader) 	partition-type:system: ext4
(bootloader) 	partition-size:metadata: 2760000
(bootloader) 	partition-type:metadata: raw data
(bootloader) 	partition-size:nvdata: 2000000
(bootloader) 	partition-type:nvdata: ext4
(bootloader) 	partition-size:frp: 100000
(bootloader) 	partition-type:frp: raw data
(bootloader) 	partition-size:expdb: a00000
(bootloader) 	partition-type:expdb: raw data
(bootloader) 	partition-size:logo: 800000
(bootloader) 	partition-type:logo: raw data
(bootloader) 	partition-size:para: 80000
(bootloader) 	partition-type:para: raw data
(bootloader) 	partition-size:keystore: 800000
(bootloader) 	partition-type:keystore: raw data
(bootloader) 	partition-size:secro: 600000
(bootloader) 	partition-type:secro: raw data
(bootloader) 	partition-size:oemkeystore: 200000
(bootloader) 	partition-type:oemkeystore: raw data
(bootloader) 	partition-size:recovery: 1000000
(bootloader) 	partition-type:recovery: raw data
(bootloader) 	partition-size:boot: 1000000
(bootloader) 	partition-type:boot: raw data
(bootloader) 	partition-size:lk: 60000
(bootloader) 	partition-type:lk: raw data
(bootloader) 	partition-size:seccfg: 40000
(bootloader) 	partition-type:seccfg: raw data
(bootloader) 	partition-size:protect2: a00000
(bootloader) 	partition-type:protect2: ext4
(bootloader) 	partition-size:protect1: a00000
(bootloader) 	partition-type:protect1: ext4
(bootloader) 	partition-size:nvram: 500000
(bootloader) 	partition-type:nvram: raw data
(bootloader) 	partition-size:proinfo: 300000
(bootloader) 	partition-type:proinfo: raw data
(bootloader) 	partition-size:preloader: 40000
(bootloader) 	partition-type:preloader: raw data
(bootloader) 	off-mode-charge: 1
(bootloader) 	warranty: no
(bootloader) 	unlocked: yes
(bootloader) 	secure: no
(bootloader) 	kernel: lk
(bootloader) 	product: ESKY6580_WE_L
(bootloader) 	version: 0.5
all: Done!!
Finished. Total time: 0.014s
Solution seems quite easy, isn't it? Install TWRP and then flash stock rom again. However, there is no information about this phone anywhere, or at least I couldn't find any. What can I do?

When I perform phone's own system check from the built in recovery, it detects the manually manipulated files (su, for instance).

When I try some other fastboot commands, this is what I get:

Code:
$fastboot oem unlock
(bootloader) Start unlock flow
FAILED (remote: 
Unlock operation is not allowed
)
Finished. Total time: 12.030s
Code:
$ fastboot oem bootlog
FAILED (remote: unknown command)
Finished. Total time: 0.008s
Code:
$ fastboot oem mmcinfo
FAILED (remote: unknown command)
Finished. Total time: 0.007s
Code:
$ fastboot oem info
FAILED (remote: unknown command)
Finished. Total time: 0.007s
This is the phone: Fiesta_I6C_V06_2015_1130


Any help will be really appreciated.
Regards.
10th December 2018, 06:31 PM |#42499  
Quote:
Originally Posted by carlosalvatore

Hi, everybody,

I rooted my Fiesta Duo I6C China phone (Fiesta_I6C_V06_2015_1130) using Kingoroot app. It went well and then I got the brilliant idea of replacing kingoroot's su for SuperSU. I followed this tutorial (Step 6 was what I did) but I got distracted and forgot to install Super SU apk (Step 6.1). I rebooted and the nightmare began. I wasn't able to boot anymore, phone stayed stuck at boot screen.

Then, I made things worse. I decided to clean my mess by performing a factory reset using the built in bootloader (Android System Recovery <3e>).


What happened? well now I have a non booting phone that does not allow adb access because USB debugging is no longer enabled.

I am a linux-only user, with moderated skills, and I am open to suggestions.

fastboot can be initiated, and both phone and computer can see each other.


More information about the phone


Solution seems quite easy, isn't it? Install TWRP and then flash stock rom again. However, there is no information about this phone anywhere, or at least I couldn't find any. What can I do?

When I perform phone's own system check from the built in recovery, it detects the manually manipulated files (su, for instance).

When I try some other fastboot commands, this is what I get:






This is the phone: Fiesta_I6C_V06_2015_1130


Any help will be really appreciated.
Regards.

It could be oem_unlock etc. Type fastboot oem help and see if that defines anything. Also if you didn't toggle the oem unlock switch in developer settings, you maybe out of luck unless you can just boot a twrp img, do your stuff and boot out of it. As for the twrp image...does your device have one?
11th December 2018, 02:30 AM |#42500  
carlosalvatore's Avatar
Member
Flag Mexico City
Thanks Meter: 4
 
More
Quote:
Originally Posted by DragonFire1024

It could be oem_unlock etc. Type fastboot oem help and see if that defines anything. Also if you didn't toggle the oem unlock switch in developer settings, you maybe out of luck unless you can just boot a twrp img, do your stuff and boot out of it. As for the twrp image...does your device have one?

First fo all, thank you for taking the time to answer my question.

Unfortunately:
Code:
$ fastboot oem help
FAILED (remote: unknown command)
Finished. Total time: 0.008s
Code:
$ fastboot oem unlock
(bootloader) Start unlock flow

FAILED (remote: 
Unlock operation is not allowed
)
Finished. Total time: 10.207s
The command above showed in the phone screen the following message (typos and everything):

Code:
Unlock bootloader?

If you unlock the bootloader,you will be able to install custom operating system software on this phone.

A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.

To prevent unauthorized access to you personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").

Press the Volume UP/Down buttons to select Yes or No.

Yes (Volume UP):Unlock(may void warranty).

No (Volume Down):Do not unlock bootloader.
Then Yes is selected and this appears.
Code:
Unlock failed... return to fastboot in 5s
This behavior occurred also prior to my problem even when I tried with "oem unlock switch in developer settings".

And sadly, my phone does not have a twrp image because I cannot find one for my brand/model.
11th December 2018, 03:44 PM |#42501  
Quote:
Originally Posted by carlosalvatore

First fo all, thank you for taking the time to answer my question.

Unfortunately:




The command above showed in the phone screen the following message (typos and everything):



Then Yes is selected and this appears.


This behavior occurred also prior to my problem even when I tried with "oem unlock switch in developer settings".

And sadly, my phone does not have a twrp image because I cannot find one for my brand/model.

I hate to say it but it sounds like it despite all what you're seeing the device does not support OEM unlocking.
Post Reply Subscribe to Thread

Tags
ask any question, beginner, confused, guidance, help needed, help thread, lost, newbie, noob, questions and answers

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes