Hi, I was on my way to root my z5p Australian version, I repaired with PC companion that also updated to Android 6 I suppose. But after update, I wanted to use my old gmail ID that I use in my other phones; however, after putting id and password it was asking for the id I've created temporarily for z5p to put that was previously synced with z5p. Unfortunately, as it was temporarily created I can't recall anything. I tried google recovery option with no luck.... can't even remember with id I used for recovery....
I've also reset it with flash tool guided through this forum, no luck.... tried to unlock boot loader from sonymobile forum by installing Android sdk. But it's failing when I put the command with the unlock code...
Is there any way that I can root my z5p or at least I can get to the phone...? Thanks in advance.....
That doesn't make a great deal of sense - did you encrypt the storage before doing any of this? If you factory reset the phone then it should 'forget' all of the Google account association and be like an 'out of the box' phone again...?
NJ72 said:
That doesn't make a great deal of sense - did you encrypt the storage before doing any of this? If you factory reset the phone then it should 'forget' all of the Google account association and be like an 'out of the box' phone again...?
Click to expand...
Click to collapse
Hi,
What do you mean by storage encryption...? I didn't do anything just updated the to Android 6 with Xperia companion. Since than I couldn't access to it without gmail account that i forgot. I read in one blog that from google has made a new security feature from Android 5 (google support for Android-one site). In that case, I've bricked my Z5P....
If none of you are able to help me, I need to through it away. I'm also ready to donate/pay for the service, if necessary. Thanks in advance.....
Hi,
Just got an idea, if Android 5 and onwards have more robust security features; is it possible to downgrade to kitkat or less, then unlocking the bootloader for rooting....? How about that...?
You won't be able to downgrade below 5.0 as that's what the device shipped with (I also doubt any devs are working on KK builds for the Z5P )
If you connect the device to your PC does it show within PC Companion? If so then try and wipe the device from there.
Can you take a picture of the screen you are presented with on boot as that should help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, it is showing on PC companion and Xperia companion. However, I don't know how to wipe off. Please let me know. Thanks
sazzadhasan said:
Hi, I was on my way to root my z5p Australian version, I repaired with PC companion that also updated to Android 6 I suppose. But after update, I wanted to use my old gmail ID that I use in my other phones; however, after putting id and password it was asking for the id I've created temporarily for z5p to put that was previously synced with z5p. Unfortunately, as it was temporarily created I can't recall anything. I tried google recovery option with no luck.... can't even remember with id I used for recovery....
I've also reset it with flash tool guided through this forum, no luck.... tried to unlock boot loader from sonymobile forum by installing Android sdk. But it's failing when I put the command with the unlock code...
Is there any way that I can root my z5p or at least I can get to the phone...? Thanks in advance.....
Click to expand...
Click to collapse
The only way to continue past this is to "remember" the Google email (and password)
Sent from my E6653 using Tapatalk
Hmm... the only wipe method using PC companion is the 'repair' option that will almost certainly still require the use of your credentials. Can you show me how far in to the system you can get? Do you have another device you can use to take a photo?
Edit: I imagine you have as you mention flashtool, but have you tried flashing a new FTF with all of the options along the right hand side ticked?
NJ72 said:
Hmm... the only wipe method using PC companion is the 'repair' option that will almost certainly still require the use of your credentials. Can you show me how far in to the system you can get? Do you have another device you can use to take a photo?
Edit: I imagine you have as you mention flashtool, but have you tried flashing a new FTF with all of the options along the right hand side ticked?
Click to expand...
Click to collapse
I'll do it again today.
Yes, I used flashtool and ticked those 4 wipe options and did it twice; till same result. Yes, I've iPhone 6s Plus and the pic I sent was taken with that....
Hi, just thinking how about formatting the phone drive a put the new rom again...! Any ideas...?
sazzadhasan said:
Hi, just thinking how about formatting the phone drive a put the new rom again...! Any ideas...?
Click to expand...
Click to collapse
I think it might be the my xperia theft protection. Google it for more information
kamalaggi said:
I think it might be the my xperia theft protection. Google it for more information
Click to expand...
Click to collapse
Yeah, it is. Google has introduced it from Android 5.0 and onwards. If it continues, some people like me has to chuck the android phones away....
Just thinking, if I use a Different stock ROM other than AU, what would happen..!! Anyone have idea...?
I don;t think moving to a different region ROM would change anything. I doubt it's the Xperia theft protection, more like Google's built in stuff.
Random-ass question, but have you actually contacted Sony support about it? I appreciate you're likely to get a faster answer out of us here at XDA, but so far our ideas haven't turned up much...
Likewise I wouldn't blatt the whole storage just to try and get in to the phone, if you can't install a ROM back on it you'll be more than buggered.
Is there any way to at least find the email address you used as your Google ID? Did you get an email confirmation to your other Google account which would at least tell you the email address?
EDIT: perhaps have a look at this page: Google Account Recovery
sazzadhasan said:
Yeah, it is. Google has introduced it from Android 5.0 and onwards. If it continues, some people like me has to chuck the android phones away....
Click to expand...
Click to collapse
If you don't mind losing data, download an Ftf for your phone and flash through flashtools. When that happens, I think you can wipe data. Thus making your phone look " out of the box"
Not sure if anyone has told this already, didn't read through the pages.
As per my knowledge, it should ask you if you want to create a new account or use an existing one, when the phone boots up.
Ashray_Vk said:
If you don't mind losing data, download an Ftf for your phone and flash through flashtools. When that happens, I think you can wipe data. Thus making your phone look " out of the box"
Not sure if anyone has told this already, didn't read through the pages.
As per my knowledge, it should ask you if you want to create a new account or use an existing one, when the phone boots up.
Click to expand...
Click to collapse
Hi, just a quick question, what is a 'ftf'..? Yes, I did flash through flashtool with 4 things checked on the top right corner. After booting it asked me to sign in and I've signed in with a new gmail ID, well new in a sense that I used it with my old Samsung S2 4G, Sony tablet and so. After putting it through I got the notification in my iPhone gmail that my ID is used to sign in to Sony Xperia z5 premium...blah...blah....On the other hand, on z5p another screen came over which was asking to put my old temporary ID that I was created at the beginning; however, I forgot the ID. I've posted that picture at the beginning if you wanna look at it. Thanks
NJ72 said:
I don;t think moving to a different region ROM would change anything. I doubt it's the Xperia theft protection, more like Google's built in stuff.
Random-ass question, but have you actually contacted Sony support about it? I appreciate you're likely to get a faster answer out of us here at XDA, but so far our ideas haven't turned up much...
Likewise I wouldn't blatt the whole storage just to try and get in to the phone, if you can't install a ROM back on it you'll be more than buggered.
Is there any way to at least find the email address you used as your Google ID? Did you get an email confirmation to your other Google account which would at least tell you the email address?
EDIT: perhaps have a look at this page: Google Account Recovery
Click to expand...
Click to collapse
Thank you so much for all those ideas, but nothing helped me. I think it is a good time to throw it away....
sazzadhasan said:
Hi, just a quick question, what is a 'ftf'..? Yes, I did flash through flashtool with 4 things checked on the top right corner. After booting it asked me to sign in and I've signed in with a new gmail ID, well new in a sense that I used it with my old Samsung S2 4G, Sony tablet and so. After putting it through I got the notification in my iPhone gmail that my ID is used to sign in to Sony Xperia z5 premium...blah...blah....On the other hand, on z5p another screen came over which was asking to put my old temporary ID that I was created at the beginning; however, I forgot the ID. I've posted that picture at the beginning if you wanna look at it. Thanks
Click to expand...
Click to collapse
I tried. But I am not able to see that image, like it's broken or something. Maybe it's just me. Could you please upload that image again?
https://mega.nz/#!c9lRjRpD!8JQWyaqzEUj9wU7d5ic3MEO_zrfpTBhekwKCTmlPy6I
Related
Okay, here's the story:
1. my phone was running WM6 and I wanted to upgrade to WM6.1 with Kavanna
2. I was installing it, but then i got error 270 (even when i did the unlocking program)
3. So Now when i turn on my phone, it flashes this white screen "Searching for SD card" then it quickly shoots to the bootloader screen.
4. I've searched probably over 10 threads, reading through 3-24 pages of information and still, nothing works.
5. When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
6. I tried getting the software from my CD that came with it, and it didn't work cause it needed Activesync to sync it
7. I tried the website, and i need the MEI-Address/code, but in order to get that, i need the phone to work, which isn't working right now.
8. IM A NOOB! I don't really know the vocabulary/slang that's being used here on the forums, but I'm trying to learn.
9. I would get a new phone, but i LOVE this phone, i don't want to give it up.
10. Any help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guy I Feel For You!
nv_lao93 said:
Okay, here's the story:
1. my phone was running WM6 and I wanted to upgrade to WM6.1 with Kavanna
2. I was installing it, but then i got error 270 (even when i did the unlocking program)
3. So Now when i turn on my phone, it flashes this white screen "Searching for SD card" then it quickly shoots to the bootloader screen.
4. I've searched probably over 10 threads, reading through 3-24 pages of information and still, nothing works.
5. When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
6. I tried getting the software from my CD that came with it, and it didn't work cause it needed Activesync to sync it
7. I tried the website, and i need the MEI-Address/code, but in order to get that, i need the phone to work, which isn't working right now.
8. IM A NOOB! I don't really know the vocabulary/slang that's being used here on the forums, but I'm trying to learn.
9. I would get a new phone, but i LOVE this phone, i don't want to give it up.
10. Any help?
Click to expand...
Click to collapse
We all know about the 270 error, guy I would never ever be rude to you. All that error is telling you that you are installing the software incorrectly. Did you take out your SD Card out of your device, before installing the software? I know the software will tell you it will automatically unlock you device, but I want you to do a SDA unlock on your phone before installing the software, then it will work, just keep a eye on your device screen and your PC screen and follow on screens instructions....................!
Now with the boot loader color screen that's another story, just because you see the color screen does not mean anything is wrong with you device, as matter of fact it's good that you seee the color screen, it's still alive, don't panic. Connect you device to you PC via active sync, it will look like it is not connect to your PC via active sync but it is, just run a old 5.0 or 6.0 software on your device, before trying to install a 6.1 ROM back on your device, it will work, been there done that...............!
I did
I didn't have a memory card in the phone, and also i did the SDAUnlock before the software
Technology said:
We all know about the 270 error, guy I would never ever be rude to you. All that error is telling you that you are installing the software incorrectly. Did you take out your SD Card out of your device, before installing the software? I know the software will tell you it will automatically unlock you device, but I want you to do a SDA unlock on your phone before installing the software, then it will work, just keep a eye on your device screen and your PC screen and follow on screens instructions....................!
Now with the boot loader color screen that's another story, just because you see the color screen does not mean anything is wrong with you device, it's still alive don't panic.
Click to expand...
Click to collapse
Follow The Above Instructions
nv_lao93 said:
I didn't have a memory card in the phone, and also i did the SDAUnlock before the software
Click to expand...
Click to collapse
The only way to get out of the color boot loader screen mode is to run a old version 5.0 or 6.0 ROM back on your device before installing a 6.1 ROM back on your device, don't panic, you are still in the game..............!
Okay, so i went to the "Official ROMS" thread, and downloaded it, When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
Technology said:
The only way to get out of the color boot loader screen mode is to run a old version 5.0 or 6.0 ROM back on your device before installing a 6.1 ROM back on your device, don't panic, you are still in the game..............!
Click to expand...
Click to collapse
Who Is Your Carrier
nv_lao93 said:
Okay, so i went to the "Official ROMS" thread, and downloaded it, When i try installing the original ROM, i get this message "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."
Click to expand...
Click to collapse
Who is your carrier and what is the brand name of your mobile device...............?
It is....
T-Mobile/T-Mobile
Technology said:
Who is your carrier and what is the brand name of your mobile device...............?
Click to expand...
Click to collapse
You Must Remove 2 Locks
nv_lao93 said:
T-Mobile/T-Mobile
Click to expand...
Click to collapse
Do the SDA unlock first again, next do a Application unlock on your mobile device, now install the old software 5.0 or 6.0, do not install the 6.1 software yet......!
Aren't those the same thing? From the "6.0 to 6.1 with pics" thread?
Technology said:
Do the SDA unlock first again, next do a Application unlock on your mobile device, now install the old software 5.0 or 6.0, do not install the 6.1 software yet......!
Click to expand...
Click to collapse
Another Thing
Explain how and what you are doing step by step when opening the RUU file?
AFTER i got the bootloader screen (red/green/blue), i went and tried to install the original ROM, and it said "the contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again.". Basically it failed.
And btw, when i tried the SDAApplicationUnlock, it says my phone isnt connected, when it is.
Technology said:
Explain how and what you are doing step by step when opening the RUU file?
Click to expand...
Click to collapse
OK I See What You Are Saying
nv_lao93 said:
Aren't those the same thing? From the "6.0 to 6.1 with pics" thread?
Click to expand...
Click to collapse
No that is not true, I will send you the other unlock file, ok!
Thanks for your help so far! =)
SDAapplication didn't work btw.
Technology said:
No that is not true, I will send you the other unlock file, ok!
Click to expand...
Click to collapse
No You Will Do 2 Unlocks
nv_lao93 said:
SDAapplication didn't work btw.
Click to expand...
Click to collapse
Wait, You don't have the other unlock app yet! I will send it to you now!
okay then.
Technology said:
Wait, You don't have the other unlock app yet! I will send it to you now!
Click to expand...
Click to collapse
In Post # 10
In post # 10 I asked you 2 questions, please explan, concerning the RUU file!
RUU Info.
Well, i'm a noob, and don't know what RUU is, BUT the only time I've encountered that problem was when i was trying to install my original ROM back on. That's all. And also it says "RUU" on the top right of the screen on my dash
ALSO: the step by steps are on post 1
Technology said:
In post # 10 I asked you 2 questions, please explan, concerning the RUU file!
Click to expand...
Click to collapse
OK
nv_lao93 said:
Well, i'm a noob, and don't know what RUU is, BUT the only time I've encountered that problem was when i was trying to install my original ROM back on. That's all. And also it says "RUU" on the top right of the screen on my dash
ALSO: the step by steps are on post 1
Click to expand...
Click to collapse
Check you PM and follow the instructions to the utmost..............!
Definitions please? Sorry
Check you PM and follow the instructions to the utmost..............!
Technology said:
Check you PM and follow the instructions to the utmost..............!
Click to expand...
Click to collapse
Personal Message(PM)
nv_lao93 said:
Check you PM and follow the instructions to the utmost..............!
Click to expand...
Click to collapse
PM (personal message) (Utmost) follow instructions to the highest degree.
Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?
cyanide911 said:
Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?
Click to expand...
Click to collapse
Humour yourself, reset again, see if it helps.
Another thing you can try doing, which I've read somewhere:
Go into Settings
App Manager
Clear data for SysScope and Enterprise SyssSope
Click to expand...
Click to collapse
If not, the other way is to flash stock firmware using odin.
Once you've flashed stock, root and use triangle away to set it back to zero then unroot by going into SuperSU and choosing "Unroot"
There are loads of threads on here if you get stuck during any steps/
Though you might to leave it before flashing firmware, your warranty is pretty useless.
When you really need to claim then you should go ahead, but until then, there really isn't much use until an update comes out.
Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.
cyanide911 said:
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available".
Click to expand...
Click to collapse
I am also little bit curious about it.
I bet it shows that Samsung somehow detected that we have modified device (root,flash, Odin...) - and prevents us from legitime update. But still dont know if I am right - also have the same notification about "modified device" since root.
I hope that in Kies there is somehow to repair device(like Sony Ericsson suite has) and this tool was able to reflash device even with unlocked bootloader
kies.
tools.
firmware upgrade and initialisation.
You must try root your device with stock recovery ery stock kernel stock rom and xposed framework
SYSCOPE MODULE
Sent from my GT-N7100 using xda premium
I experience almost the same thing,. I got my note2 from my service provider,. i had never rooted the phone since its still under warranty, however, there are times when i try to check for an update it warns me that i cant do OTA because my device has been modified. and on the status itself it says modified. Restarting my phone fixes this, the status goes back to "normal". It's just irritating to know that it says its modified although for a fact i know I never did. It's hard enough to resist the itch to root then the phone slaps you in the face making this kind of jokes on me.. looks like its teasing me (because this is the only mobile phone I had that I refused to root/flash for the meantime).. lol
I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nameless21 said:
Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.
Click to expand...
Click to collapse
Second that. Just finished "clean up"...
---------- Post added at 07:12 PM ---------- Previous post was at 07:08 PM ----------
cyanide911 said:
I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
Click to expand...
Click to collapse
I didn't see XXX before. As you're on 4.1.1 you may use CSC changer without root. But definitelly change your CSC (best if you pick CSC for the country where you are). There's a list of CSC's in the forum, search and change. Then reflash ROM via KIES and it'll be clean
It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).
cyanide911 said:
It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).
Click to expand...
Click to collapse
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium
aspot72 said:
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah just downloaded the INU firmware, I'll go ahead with it. One more thing that I noticed in this whole process.
My phone's IMEI behind it's battery is different to the IMEI it displays inside the phone. After some brief googling, it seems it's either improper flashing or maybe an unofficial mainboard installed am I right?
When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.
dr.ketan said:
When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.
Click to expand...
Click to collapse
Okay this is getting extremely strange. I flashed the latest 4.1.2 ROM for INU from Sammobile via ODIN. Everything works well except, well, the phone! I can't make any calls or texts or even receive any. If someone else calls me, my phone rings at their end but nothing happens at my end. Nothing at all. If I try to make any calls it says "Not registered on network".
I tried fiddling around in mobile networks in the settings, but nothing makes it work.
What the hell? I can't help but think this is something related to that IMEI number thing.
Very suggestive of your IMEI get banned.
Can you tell me first 5-7 digit of IMEI you seeing in device setting?
(Don't put full imei on public forum)
If your imei in setting is starting with
00499 then it is generic.
Sent from my GT-N7100 using xda premium
Hmm, I used this patch after rooting and installing busybox:
http://forum.xda-developers.com/showthread.php?t=1918601
And now everything seems to be working fine. And now my device status is back to 'Modified' haha.
So what does all this mean? My IMEI number being different in the phone and behind the phone? And I don't even know what that patch above 'fixed', but it fixed my network issue.
None of the two IMEI numbers above are starting with generic type IMEI...
That's good
I said earlier your imei changed due to unauthorized mobo replacement, samsung ppl replace old imei if they change mobo.
So in that case it is repaired by unauthorized person (which can just cause problem in warranty) but not unofficially.
If still your csc is unknown then flash same rom with CSC tab in odin instead of PDA (which may factory reset, so make backup of your imp data)
Still it remain xxx in kies, then may be efs is corrupted and only previous backup is savior.
Sent from my GT-N7100 using xda premium
your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.
your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.
I've recently bought this tablet for storing books and such for school and such that I won't have to carry around an extra 10 kilograms in my backpack. The Ematic Genesis Prime is a very basic Android Tablet that you would most probably find on eBay, Alibaba, etc. I've been trying to find if rooting was possible on this device. I've heard this saying - "Everything is possible on Linux", and so was rooting this tablet. While I was browsing around threads, I've found a way, and decided to make this guide, such that everyone who looks for the method will find it easily.
Rooting Guide
To root this tablet, we will be using Cydia Impactor -
Cydia Impactor is a GUI tool for working with Android devices. It has features already, but is still very much a work-in-progress.
Right now, its key feature is an end-to-end exploit of the Android "Master Key" vulnerability, allowing a user to obtain root access on many Android devices (including Glass and TV).
- http://www.cydiaimpactor.com​
Click to expand...
Click to collapse
I have done this method of rooting on my EGS004-BL. It should most work for other colours. (-BL or anything after the - dash is your colour, so in my case, it is black. ) It would most probably work for the other variants such as EGS102 (Genesis Prime XL), and EGW004 (Waterproof version of the EGS004).
Before you start:
I am in no way, shape or form, responsible for the outcome, positive or negative, of you following the provided instructions on this thread.
It worked for me, but that does not mean it will 100% work for you.
You are responsible for any side effects and damage caused to your device, your property, anyone nearby, or yourself, which includes, but not limited to, robbery, riots, injury, death, acts of god, epidemics/pandemics, natural disasters, government shutdowns, mutations, growing an extra arm or any limb, etc.
Rooting will void your warranty.
Preparing to Root
First, you will need to download the program from its website. The download links are in bold letters so it should stand out. The website is at http://www.cydiaimpactor.com
Once the download has finished, extract the .ZIP file onto your Desktop (or whichever folder you like).
Now, move over to your tablet. Hit the settings icon from your desktop or app drawer. Go to { } Developer Options.
One you're there, make sure that the options are on with the 'switch' on the top right corner of the screen. If not, tap it and turn it on.
Once the Developer Options are set to ON, check off USB debugging. Tap OK when the "Allow USB debugging?" window pops up. Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting
Using the USB cable, connect your tablet to your computer. Then, go to the place where you extracted Cydia Impactor and open it.
Once Cydia Impactor is open, click on USB and then Driver Scan. If you are asked to select which device/port, chose the right one and hit OK/Yes. Wait until it installs the drivers. NOTE: You may be asked to reboot your computer. If so, reboot first, then continue to the next step. Screenshot:
Once that's done, click Start in Cydia Impactor. DO NOT CHANGE THE TEXT IN THE TEXT BOX. It should try to root the tablet with the methods that it has in store. Wait until it roots your tablet.
Once it says it successfully rooted your tablet, reboot it for safety's sake. (You don't have to, but just do it anyways).
After your tablet has started up, open up Play Store and download a Superuser program. I personally like Chainfire's SuperSU.
After installing a Superuser program, it may ask you to update the SU binary. Please hit OK/Yes and let it update.
That's it! Your tablet has been (or should be) rooted! If you want to check, you can download Root Checker from the Play Store.
CWM Recovery
@dolorespark has created CWM Recovery for A10/A13 Tablets. The EGS004 is an Allwinner A13 Tablet so use the A13 version of it.
It's here: http://forum.xda-developers.com/showthread.php?t=2189640
Custom ROMs
There is an unofficial CyanogenMod 10 for the tablet (meant for generic A13 tablets) available at: http://forum.xda-developers.com/showthread.php?t=2343531
Known Issues
- On EGS 102 (XL PRIME), Cydia Impactor will report an unsuccessful root job, but will actually root the tablet. (Thanks to @oldsoldier2003)
Hit the thanks button if I've helped you. If you ran into troubles, have suggestions, or just want to say that it worked, please don't hesitate to reply.
Finally!!!
Hey thank you so much...I Testify that this rooting is 100% safe and successful on my EGS004-bl from my experience... i am new here i just register say thanks :good: :laugh::laugh:
One small issue noted on the EGS 102 (XL PRIME). Impactor didn't report a successful root job, but did indeed root the tablet. Thanks for the quick guide and pointing out this tool.
as i am used to rooting name-brand android devices...this actually works, and quite easier than galaxy devices...my wife got this for me...we dont have a lot of money so couldnt get a nexus...its a little slow responding, but hopefully there is a rom that can speed it up...but this works quick and easy and don't even have to copy files over...thanks...
It may be awhile before you can find a ROM for it because most of the talented devs are quite busy on other devices that are more popular. It is my hope that these devices become a little more popular and get some love here too
Sent from my EGS102 using XDA Premium HD app
oldsoldier2003 said:
It may be awhile before you can find a ROM for it because most of the talented devs are quite busy on other devices that are more popular. It is my hope that these devices become a little more popular and get some love here too
Sent from my EGS102 using XDA Premium HD app
Click to expand...
Click to collapse
There's an unofficial ROM - http://forum.xda-developers.com/showthread.php?t=2343531
recoveries
Has anyone found a recovery for this tablet yet or one that is comparable,so we can back up and restore them if something gets fubared
ed196741 said:
Has anyone found a recovery for this tablet yet or one that is comparable,so we can back up and restore them if something gets fubared
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2189640
There^
Also updated on the OP. (Thanks for the reminder, it's been here for a while, just didn't get around to adding it )
Thanks, now I have some more questions !
We recently purchased a EGS114 its a Ematic Genesis 2 , we used your guide to root it and it worked out great, thanks! Now what do i do, basically I'm saying this is brand new to me, I've put Nova Settings on there and it made it look better, have the Superuser chain fire, but really kinda at a loss of what to do. I understand this might be in the wrong location but I cannot find any information on these tablets, this is the sole reference to the Ematic series i have found and one you tube video showing gibberish. What i would like to do / plan is Ive seen videos on making your external SD card your internal so i can have more app space - Have a 32gb Micro SD Card in route, plan on partitioning it and all really no idea but you tube helps. Secondly saw on how to use the sd card for your Ram to speed up applications plan on trying that. Also I've been trying to overclock the CPU but cant, I believe i need to change the kernel or ROM something or other, i have no idea how to do this??? Well that's some of what i believe is possible with this device if you guys could help me out i would really appreciate it . Try not to bash to hard on the new user that i am i apologize in advance.
:fingers-crossed:SweetAction​
SweetAction said:
-snip-
Click to expand...
Click to collapse
Looking to do the same! If you find links, mind posting here, or making a how-to comment? would love to do more with this thing!
PS: in Linux, simply running Impactor after extracting it wasn't doing it for me, I had to hop in terminal and run it as su (sudo ./Impactor, after navigating to the folder). It then ran just fine, with no problems. Ends up I needed the adb server to be started as root(sudo adb start-server as opposed to adb start-server), otherwise it gave me the finger - aka ????????? - no permissions.
SweetAction said:
We recently purchased a EGS114 its a Ematic Genesis 2 , we used your guide to root it and it worked out great, thanks! Now what do i do, basically I'm saying this is brand new to me, I've put Nova Settings on there and it made it look better, have the Superuser chain fire, but really kinda at a loss of what to do. I understand this might be in the wrong location but I cannot find any information on these tablets, this is the sole reference to the Ematic series i have found and one you tube video showing gibberish. What i would like to do / plan is Ive seen videos on making your external SD card your internal so i can have more app space - Have a 32gb Micro SD Card in route, plan on partitioning it and all really no idea but you tube helps. Secondly saw on how to use the sd card for your Ram to speed up applications plan on trying that. Also I've been trying to overclock the CPU but cant, I believe i need to change the kernel or ROM something or other, i have no idea how to do this??? Well that's some of what i believe is possible with this device if you guys could help me out i would really appreciate it . Try not to bash to hard on the new user that i am i apologize in advance.
:fingers-crossed:SweetAction​
Click to expand...
Click to collapse
indestructibleguy said:
Looking to do the same! If you find links, mind posting here, or making a how-to comment? would love to do more with this thing!
PS: in Linux, simply running Impactor after extracting it wasn't doing it for me, I had to hop in terminal and run it as su (sudo ./Impactor, after navigating to the folder). It then ran just fine, with no problems. Ends up I needed the adb server to be started as root(sudo adb start-server as opposed to adb start-server), otherwise it gave me the finger - aka ????????? - no permissions.
Click to expand...
Click to collapse
Sorry for the VERY late reply. My xda account is currently hooked up to my gmail which I don't really check anymore because I have my own domain name & an email address on that.
Regarding the overclocking issue:
Yes, you cannot overclock this device. Mine came underclocked actually - NoFrills CPU Control was showing 1.008 GHz instead of the claimed 1.5 . I was able to bump the value up to 1.2 before the app would crash after hitting 'Apply'.
There is an unofficial CM Rom for this tablet - http://forum.xda-developers.com/showthread.php?t=2343531
(I tried flashing this but I derped and now the tablet itself is bricked and there's no way I know to fix it other than buy another one, which I won't do.. I probably forgot to clear the cache which is why I bricked it).
I believe you can overclock after installing that ROM (unless it already does it for you).
SweetAction said:
We recently purchased a EGS114 its a Ematic Genesis 2 , we used your guide to root it and it worked out great, thanks!
Click to expand...
Click to collapse
I have a quite recent EGS114 and it's a substantially different tablet than the EGS004, having an ARMv7 CPU, more RAM & memory, etc.. I am wondering if this model number has been recycled with a different tablet and the EGS114 you got is different than mine -- and if this root procedure will still work.
The original message is quite old and the graphics are 404ed out.
If anyone has any suggestions for rooting this unit, I'd be grateful:
Model: EMatic EGS114
CPU: ARMv7
Android: 4.0.4 ICS
Kernel: 2.6.34
Does anybody know if this works on the Ematic EDG103?
I too have got the EMatic EGS114/ Android: 4.0.4 ICS/ Kernel: 2.6.34. Purchased from TigerDirect.
The current memory {RAM allocated} is poor for APPS. Not sure what to do with this tablet. .
Any success on rooting the tablet ?
JohnLNU said:
I have a quite recent EGS114 and it's a substantially different tablet than the EGS004, having an ARMv7 CPU, more RAM & memory, etc.. I am wondering if this model number has been recycled with a different tablet and the EGS114 you got is different than mine -- and if this root procedure will still work.
The original message is quite old and the graphics are 404ed out.
If anyone has any suggestions for rooting this unit, I'd be grateful:
Model: EMatic EGS114
CPU: ARMv7
Android: 4.0.4 ICS
Kernel: 2.6.34
Click to expand...
Click to collapse
Judging by the last comment (on the OP's post), this looks like it works on the EGS102 as well?
No Volume Buttons
Hello all,
I have gotten as far as getting CWM onto my EGS004, but I have arrived at a problem: the EGS004 does not have volume up/down buttons, so I have no way of doing anything in the recovery menu. Is there something I am missing, because I can't find a way to navigate the menu in CWM via touch.
thexfactor04 said:
Hello all,
I have gotten as far as getting CWM onto my EGS004, but I have arrived at a problem: the EGS004 does not have volume up/down buttons, so I have no way of doing anything in the recovery menu. Is there something I am missing, because I can't find a way to navigate the menu in CWM via touch.
Click to expand...
Click to collapse
Just attach an USB keyboard to the tablet, but don't bother, I flashed that custom firmware on my laptop and now it is bricked and I'll need to figure out a way to boot into CWM without using adb or the volume button. Oh well
biscoito1r said:
Just attach an USB keyboard to the tablet, but don't bother, I flashed that custom firmware on my laptop and now it is bricked and I'll need to figure out a way to boot into CWM without using adb or the volume button. Oh well
Click to expand...
Click to collapse
I figured another method out: there is a tiny pin-reset button hole above the USB port on the left. This can be pressed with a paper clip to cycle through menu items in the recovery. I haven't tried, but I'll bet you could boot into recovery by holding power+pin-reset.
thexfactor04 said:
I figured another method out: there is a tiny pin-reset button hole above the USB port on the left. This can be pressed with a paper clip to cycle through menu items in the recovery. I haven't tried, but I'll bet you could boot into recovery by holding power+pin-reset.
Click to expand...
Click to collapse
The pin-reset method you mention did not work, and I didn't a make a livesuit suitable backup before I flashed my tabled. I only backed up using CWM and they are not compatible with each other. Would you mind uploading a rom dump of you tablet so I can try to make a flashable rom in order try to save my tablet ? I found these instructions on how to do it http://www.imajeenyus.com/computer/...et/android/livesuit_creating_final_image.html
Hi, i have an ematic egs114 and i want to install a cwm recovery but i dont know which one i have to install and since it wont boot i dont know how to figure it out either, can anyone helpme please????
My Pixel 2XL has locked bootloader and from yesterday I'm having some issues with touchscreen not responding. I spill some coffee on display - just a few drops of cold coffee - but quickly wiped out. The phone was OK, but in the evening the touchscreen stopped working. My first impression was that's a beta issue and so I manually wiped device but it didn't help, the screen is still not reacting.
So before I tear device to see it's not a hardware issue I would like to try to downgrade to stable android 9. Because bootloader is locked my only option is to update/downgrade via ADB, but because official OTA for Android 9 is older ADB is not allowing me to downgrade.
From what I read, rolling back to stock involves sing-off from the beta program on Google's website and wait for another OTA to revert to stock, but because I wiped the device and can't even set the system up and running I won't get it.
Maybe someone can provide such OTA file? Or maybe I'm doing something wrong.
Please, guys, help me out.
Files are here https://developers.google.com/android/images
Droid_Nut said:
Files are here https://developers.google.com/android/images
Click to expand...
Click to collapse
Because my bootloader is locked I just can't flash system image and so far there's no method to unlock Verizon variant. Only OTA newer than Q beta4.
What happens when you try to wipe/format data from the recovery partition? Having a corrupt system/OS shouldn't have affected the recovery partition and/or the ability to format and wipe it to a stock state...
But, if anything, you might have some luck downloading the OTA system image (can still be found at the developers site of Google's), loading up the stock recovery (don't worry if you get a dead droid with an exclamation/triangle, it's supposed to show that, you just need to hold Power + Volume-Up at the same time), and running through the selection of "Apply update from update" and/or "Apply update from .zip" where you can now either point to the OTA .zip manually or "push" the file onto your device...
Using the stock recovery to either wipe/format the device or manually applying the OTA seems to be the only rescue method available to locked bootloader devices...
Good luck to you and I hope this helps...
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Edmontonchef said:
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Click to expand...
Click to collapse
My touchscreen doesn't work, so I can't pass the initial set-up.
I just hope Google will release DP5 within a couple of weeks. Or maybe the touchscreen is broken? I guess I have to wait.
BTW Now I'm rocking old Lumia 550 on WM10 and it's a real pain in the a.ss without google services.
lywyn said:
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Click to expand...
Click to collapse
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Maybe someone could upload it's "un-roll" OTA. So I could try to flash it and find out is it software or hardware issue.
adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
lywyn said:
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
Click to expand...
Click to collapse
I know that, but IP rating doesn't mean that your phone is absolutely 100% safe, and maybe this time I got run out of luck.
I'm just patiently waiting for beta 5 to be announced and then we'll see.
simplepinoi177 said:
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
Click to expand...
Click to collapse
It's exactly like You said. I'm able to flash Android Q beta DP4 OTA, but after rebooting I'm stuck at welcome screen and the touchscreen doesn't work.
But once, when I removed the SIM card and popped it right back, a popup window for SIM unlock appeared and I was able to input pin (after that screen got frozen), so I believe that's not a hardware issue. I just have to wait for DP5 and find out is it gonna help or not.
Use an external mouse via USB adapter to pass the welcome screen etc
siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
I didn't know that. Thanks for the tip.
siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
So I did. With the mouse, I was able to sign in Google account and unroll from the beta program. I immediately received OTA with android 9 form June, but after a downgrade, my touchscreen still doesn't work.
How the heck is it possible? The screen is connected to the motherboard with only one ribbon, so if that ribbon would be defective, the screen should not turn on or have some artifact.
So far it's working OK, except for some strange glitch with "day widget".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions? Should remove the screen and see what's inside? I guess that's the only option left.
Probably your screen is broken and you need a new one. Warranty?
siggey said:
Probably your screen is broken and you need a new one. Warranty?
Click to expand...
Click to collapse
Nop, device bought in Best Buy i NY. So would have to bring it overseas from Europe, because in my country Google doesn't sell devices.
I was trying to unbrick my Xiaomi redmi note 8 pro, i have bricked it twice before and both times had to pay someone with an authorized Xiaomi Service Account, well this time i figured id wait for someone to come out with a method that works and id just use my samsung phone until then, well i waited and waited , and eventually i see the mega tread with the anti-brick in it. I was happy but for the few poor schmucks out there that never had a chance to flash that beautiful set of files i found a way out without paying someone to fix your screw ups.
Anyway I've tried lots of things to unbrick it, removing the battery , replacing the battery anything to get my back to fast boot. I've attempted flashing stock a countless amount of times in different ways and today i needed money very bad to pay some bills so i figured id try to fix it one last time so i could sell my note 10 +. I never had a chance to install the antibrick or whatever it is so theres no way this is just a fluke. I would like to give myself no credit anything here besides finding the files and making the guide. I feel bad because people are charging 35 bucks to practically login for you, and id really be a bad guy if i didnt post what ive found today. Well enough of the backstory here's a guide and ill link what worked.
I will provide the download for all the files you will need here.
https://drive.google.com/file/d/1RWwwUEZJnxmSzZMbFj5_zJaGQ1OJAFo5/view?usp=sharing
This guide is for the Global Version but its the same on all your just sub out the global ROM I've provided with my other files for the one in your region
After you have the zip file containing the files needed do as follows.
1. Uninstall your Current Mi-flash / MiFlashpro
2. Extract the .zip folder
3.Install The Miflashpro that i have in the zipped folder
4. Launch Miflashpro and login.
5.After your are logged in launch Spflash.
6. Inside SpFlashTool click the options tab in the top bar, second column from the left , then click options to open the settings , click general, then in the general tab you want to make sure check lib da match is unticked.
7. Now to begin flashing, Match up the .da file and the .auth file with the ones in the special sauce folder of the zip folder you downloaded , after thats its like installing stock "normally", if you are on global the scatter file is in globalromfiles/images directory.
8. When everything is setup simply click download.
9. As a few disclaimers I tried 6 or 7 times before it worked, i dont remember if i had spflashtool set to firmware upgrade or download download only, i will also state that it failed ounce or twice in both, i just held power and volume up until it cycled i head the ding on my pc letting me know windows picked it up and i had device manager open so i could see the mtk preloader and com ports, i was very surprised when it worked but it did. Anyway if this helped anyone please spread the work so people can know that there phones are not at the mercy of someone else's login. If you have any questions or issues please reply to the post ill respond as quick as i can. I'm not a developer just a modder if anything. I know basic python and how to screw up my phone stumbling upon a fix took me weeks or months even of on and off boredom spikes but this worked for me.
Anyway if this helped at all spread the work , and feel free to donate to me on cash app $KaozCash
hi
works with 64gb and 6gb ram version?
Rebellion747 said:
works with 64gb and 6gb ram version?
Click to expand...
Click to collapse
Yes That is what i originally did it on , the begonia model
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
angrypandagr said:
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
Click to expand...
Click to collapse
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
sawclan22 said:
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
Click to expand...
Click to collapse
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
angrypandagr said:
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
Click to expand...
Click to collapse
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
sawclan22 said:
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
Click to expand...
Click to collapse
I hate to ask but I need a test subject this worked for me but I may have left something out in my steps I could just brick my phone again a try it again myself, but it probably wouldn't be the same because the first the I did after making this thread flash the abtibrick lk and preloader, if you have some alternate way I can talk to you without using this thread I would love to fix it for you if I can, I want this guide the be revised to be a simple but highly detailed guide on how to fix this issue, it worked for me when I did it and I want to be able to help others. I just need someone else with a bricked device to test it too and for me to make sure that it's exactly what I did.
Thanks from my heart
bro your method if it works thank you very much, you saved me
Rebellion747 said:
bro your method if it works thank you very much, you saved me
Click to expand...
Click to collapse
Did you end up fixing your device? I figure if people report back success than more people will see it
Not working
I followed your instructions and did it several times but nothing seems to work for me
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please find a alternate way or help me.
Thanks for the thread .
RanaDARK said:
I followed your instructions and did it several times but nothing seems to work for me
.
Please find a alternate way or help me.
Thanks for the thread .
Click to expand...
Click to collapse
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Lajbymester said:
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Click to expand...
Click to collapse
have you guys tried to use edl? if not, try doing edl mode
Please
Hello, could you tell me the contact privately if you need who unlocked it for you? Although this is being advanced, I need the mobile quickly and I would appreciate it very much.
not work for me, the sp tools keep show up notification to login mi account
my phone brick because I downgrade from android 10 to android 9
need help asap guys
sawclan22 said:
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
Click to expand...
Click to collapse
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
can u please upload only flash tool files
I had already downloaded the rom ...im in my village (due to lockdown) with slow internet /nowifi so can u please upload flash tool only so I can test it
Not Work for Me :/
After trying the method with your files, the problem is still the same, the authentication window comes out every time and I can not flash my phone, for information (without Flash Tools) my phone displays only the LED light and when I connect it on my PC my computer recognizes it for a few seconds and this disconnection, maybe we don't have the same Hard Bricked of the phone
if you have any other information to suggest to me I will be grateful, thank you
(by google translate)
RanaDARK said:
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
Click to expand...
Click to collapse
No it was definetey hatdbricked, stuck in a brick state after flashing an improper boot.IMG I was getting the error for authorization myself , then the window popped up with that specific set of tools and files , I then logged into my personal account and it worked, I tried flashing a good bunch of times, I removed my battery I couldn't get back to fastboot mode eventually I downloaded that mi flash tool from cynagenmods website , they called it a preauthorized flash tool or a flaehtool that wouldn't require authorization , well it didn't work I found the files in the special sauce folder in somones github , it would let me use them so I unticked something in the settings of sp flash tool , I can refer to the guide to see what it was after that I was super surprised to see it flash , maybe every other time I tried to flash it was a driver issue , if multiple people answer this the same let me know so I can close this thread, when u flash your hardbricked device does it even attempt to flash at all , do u see the loading bar move , usually it would fail for me on the first file it tried flash and I want to know the specific error it gave , this was my second time doing something idiotic and hardbricking this phone , if anyone can download teamveiwer and let me make sure all drivers are the same all files are exactly what I have etc , spflashtool has a good bit of different errors , I can't retest myself , not accurately atleast, the first thing I did after unbricking my phone was flashing the antibrick lk.IMG and bootloader