This is what I get after running simple oem unlock command via adb
{
"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"
}
Can it be unlocked now?
I was running on 7.0.4.0 Stable - stock out of box, just rooted straight from 3rd party dealer.
Just to update, now I just disconeccted the device from PC and it cant boot. But it worked 4-5 times before, as I was checking bootloader status after few reboots.
PC sees it as QHSUSB_BULK. It's a hardbrick. Any advices?
From what you've done there, nothing should've changed on the device. It was already unlocked, it comes unlocked out of the box.
What else did you do and what do you mean when you say it can't boot? What happens when you hold the power button for a few seconds? Can you still boot into the bootloader (pwr vol -) or the recovery (pwr vol +)?
It's not a hard brick as long as you can still run fastboot, which should work seeing as that's all you've done.
If it's just the PC not recognizing you could try rebooting, clearing adb and device drivers (you can show hidden hardware in the devices management to find your drivers) and reinstalling them.
Logic_ said:
From what you've done there, nothing should've changed on the device. It was already unlocked, it comes unlocked out of the box.
What else did you do and what do you mean when you say it can't boot? What happens when you hold the power button for a few seconds? Can you still boot into the bootloader (pwr vol -) or the recovery (pwr vol +)?
It's not a hard brick as long as you can still run fastboot, which should work seeing as that's all you've done.
If it's just the PC not recognizing you could try rebooting, clearing adb and device drivers (you can show hidden hardware in the devices management to find your drivers) and reinstalling them.
Click to expand...
Click to collapse
UPDATE:
Flashed 7.1.6.0 Stable.
Lost root.
All data and apps present.
Got Chinese apps now.
Google services not working.
It didn't react to whatever I did. Just now I tried holding vol - & power buttons for a minute or two and I got into fastboot. Just reflashed image via miflash and waiting to boot. I see Mi logo and a progress bar loading.
Will report on the outcome.
voolandis said:
It didn't react to whatever I did. Just now I tried holding vol - & power buttons for a minute or two and I got into fastboot. Just reflashed image via miflash and waiting to boot. I see Mi logo and a progress bar loading.
Will report on the outcome.
Click to expand...
Click to collapse
you are doing right but beware 6.xx latest developer rom, it will lock your bootloader and stock recovery again .
voolandis said:
UPDATE:
Flashed 7.1.6.0 Stable.
Lost root.
All data and apps present.
Got Chinese apps now.
Google services not working.
Click to expand...
Click to collapse
Yes, the stable does not have root. You can choose where to go from here, if you want to push the files for root and gapps yourself, or go with a new ROM entirely.
In any case what is most advisable right now is flashing a custom recovery (TWRP) so you have much more control and a bit of extra safety to know that you can more easily recover if you bootloop.
Logic_ said:
Yes, the stable does not have root. You can choose where to go from here, if you want to push the files for root and gapps yourself, or go with a new ROM entirely.
In any case what is most advisable right now is flashing a custom recovery (TWRP) so you have much more control and a bit of extra safety to know that you can more easily recover if you bootloop.
Click to expand...
Click to collapse
Fixed Play Services by complete removal and fresh install from MIUI store.
Is there any way I can actually check if my bootloader is locked or not?
Will flashing TWRP (if BL is locked) lead to brick, or will it simply fail and phone will work?
You checked if your bootloader was unlocked in the first post, that's what
Code:
(bootloader) Device unlocked: true
means.
Only flashing the official dev builds (for now) will lock your bootloader. The version you installed should not have locked it.
A locked bootloader will make flashing TWRP impossible. So just be sure to stay away from those official dev ROM.
Logic_ said:
You checked if your bootloader was unlocked in the first post, that's what
Code:
(bootloader) Device unlocked: true
means.
Only flashing the official dev builds (for now) will lock your bootloader. The version you installed should not have locked it.
A locked bootloader will make flashing TWRP impossible. So just be sure to stay away from those official dev ROM.
Click to expand...
Click to collapse
All good. Flashed TWRP (it's got that no response bug every time it boots), rooted.
Will go for sMIUI now.
Related
My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Faizan.Waheed said:
My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Click to expand...
Click to collapse
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Plz Help
ej8989 said:
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Click to expand...
Click to collapse
Yes i did install the PdaNet Drivers and then unlocked it that but still it is somehow locked... The thing is that when i simply turn on phone it stucks with the google logo on it. Then any command that i may type is just ineffective.. Command windows says "Device searching" but if i start the phone in bootloader menu then computer recognizes the device.....?? i just cant figure out what to do.......I have been trying to sort this issue since last monday but all in vein...
So any solution that might entertain this problem
Go to bootloader, flash a custom recovery, then flash a new rom.
ej8989 said:
Go to bootloader, flash a custom recovery, then flash a new rom.
Click to expand...
Click to collapse
Thank you so very much for your concerned and valuable advices.... i Really appreciate it but
PLz can u direct me through some instructions that how to flash a custom recovery and then flash a new room...? What soft wares i will be needing and wht will the procedure........??
amydacus3 said:
Central and elegant location.
{
"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"
}
Click to expand...
Click to collapse
Didn't get you bro.....??
help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S
prasse said:
help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S
Click to expand...
Click to collapse
How long did you let it sit on the Asus screen?
Which recovery and version?
I've seen my tablet take 45 minutes to boot on older versions of TWRP after a ROM flash.
This hasn't happened for quite a while however.
This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?
sbdags said:
This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?
Click to expand...
Click to collapse
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s
prasse said:
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s
Click to expand...
Click to collapse
Do yo usee ANY number flying about giving any indication as to what bootloader you're on? sbdags made an important point -- you'll need a current bootloader version to get the more recent ROMs working.
Oh, and ehh... please use interpunction -- you know, periods and commas and stuff. It makes a sentence that much more readable and understandable.
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?
sbdags said:
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?
Click to expand...
Click to collapse
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.
prasse said:
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.
Click to expand...
Click to collapse
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.
sbdags said:
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.
Click to expand...
Click to collapse
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?
prasse said:
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?
Click to expand...
Click to collapse
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?
prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
How do you know you're on TWRP if you can't get into recovery?
sbdags said:
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?
Click to expand...
Click to collapse
okay thank you for the explanation, but no i dont have fastboot avaliable.... got the same screen as before.
ngionla appearance
Thats OK said:
How do you know you're on TWRP if you can't get into recovery?
Click to expand...
Click to collapse
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.
prasse said:
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.
Click to expand...
Click to collapse
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
{
"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"
}
Is it anything like the above image?
Thats OK said:
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
Is it anything like the above image?
Click to expand...
Click to collapse
Ye almost the excat same, i Can upload a picture when i get home... But no i dont know the difference between, your mentioned wipes sorry :s..
If it looks like that what happens when you push volume up on the RCK icon?
sbdags said:
If it looks like that what happens when you push volume up on the RCK icon?
Click to expand...
Click to collapse
see thats the difference, i only got the two last icons wipe and usb : /
That sounds like you do not have any recovery available. If you connect the tablet to the computer via SUB and pick the USB option, what happens?
Isn't the fastboot built into the bootloader? It should be always possible to recover if you can get to the recovery select screen and select fastboot, shouldn't it?
hello every one
i have Nexus s m200 and suddenly i found my phone switch off and when i tried to switch it on it stuck on Google logo
then i tried to on it with volume(-) and power button then i found android logo with this
{
"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"
}
then i tried to check adb device but not found my device but i can found my device as fastboot so i boot it with boot loader volume (+) and power button ever thing was fine i tried to restore with official rom but not able to do because oem was locked i tried to unlock it but always fail and here the main problem begin
i treid several time but not successful with it so i restart phone with both volume key (-).(+) and power key
then i redierct to cwm and there i wipe cache and davlik last two option not remember the second last one and after that
my phone was not able to communicate with pc and boot loader screen also freeze am not able to up and down with volume key or not able to select any thing with power key
then i pulled my battery push power button to drain any power source then after few min i tried again but same phone is freeze with bootloader screen or else on Google logo no adb no fast-boot access
one more thing when phone is on google logo i check usb dview there it show google mass storage but not show storage device on my computer
i have padnet and also my driver is install so there is no driver problem as it already connected in fast boot mode earlier
Problems
bootloader freeze
oem unlock
stuck at google screen
no adb devices and fastboot devices found after wipe
i tried lot of search and every single tutorial present on net but not yet solved my problem so i decide to share it with you
hope for best
last thing i want to know if i go with ubunto tutorial do i have to uninstall winodw to install ubunto or is that application for windows
need help guys plz help me my phone is not more then a paper weight
Nexus toolkit is a free program for windows.. Download it and follow tutorial.. If you get stuck message me..
Sent from my Nexus S using xda premium
Setting.Out said:
Nexus toolkit is a free program for windows.. Download it and follow tutorial.. If you get stuck message me..
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
as i said i have tried every single way wich provided on net as well nexus toolkit too
am not able to comunicate with pc and phone
no adb device found and no fastboot at all
at bootloader screen mobile freeze too
iqbalusmani said:
as i said i have tried every single way wich provided on net as well nexus toolkit too
am not able to comunicate with pc and phone
no adb device found and no fastboot at all
at bootloader screen mobile freeze too
Click to expand...
Click to collapse
Setting.Out said:
iqbalusmani said:
as i said i have tried every single way wich provided on net as well nexus toolkit too
am not able to comunicate with pc and phone
no adb device found and no fastboot at all
at bootloader screen mobile freeze too
Click to expand...
Click to collapse
I know this is frustrating, but as I can't know all what you know I'll need to question what you've done.. And repeat steps..
Power phone off, pull batt and sim, let sit for five min., replace batt and sim, boot only to boot loader, connect to PC, open nexus tool kit, select flash to stock bricked version, if it can't recognise phone use other USB port try again.. This should work.. You won't have a custom recovery so if you try to boot into recovery after stock flash there will be dead android, not a big deal, just use toolkit to flash new recovery..
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
problem is mostly solve now i had back to pc conectivity did it with Riff Box
now my boot loader screen is not freeze i have fastmode device connectivity
but no adb yet
and am not able to unlock with fastboot oem unlock
its give me
C:\Users\hp>fastboot oem unlock
...
FAILED (remote: Erase Fail)
finished. total time: 1.510s
riff box also not able to load boot loader
so now i am able to move in stock recovery and have adb sideload
got ad connection
my bootloader is still locked
do you guys recommend me to use adb side load to flash my rom
sent my phone to samsung outlet hope for best
Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL
More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"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"
}
This is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
what about off warranty repair by alcatel service in your country?
N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases
Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
So my litlle brother played with my phone .When it was doing a software update and somehow turned it off.And now when i try to turn it on it shows me some green dots and then shuts down.
When i am charging it it also shows green dots .If someone could help me thanks in advance.
{
"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"
}
VIDEO LINK
download mode or recovery mode doesn't work, it keeps turning on with the green dots on it
I'm afraid that Samsung Support is now your only option, seems like You've tried everything you could do on your own without voiding the warranty. As last resort, try extra dry it since it was in fact left unattended, then try download mode once more after.
NetBos said:
I'm afraid that Samsung Support is now your only option, seems like You've tried everything you could do on your own without voiding the warranty. As last resort, try extra dry it since it was in fact left unattended, then try download mode once more after.
Click to expand...
Click to collapse
Yep, best suggestion for now
Can someone explain what the "green dots" mean?
GalaxyA325G said:
Can someone explain what the "green dots" mean?
Click to expand...
Click to collapse
something to do with corrupt drivers, look at the picture and you will see some green bars
Hold volume up and down plus side key together will take your to download mode don't plug in USB cable
hold v+ v- and side key said:
Hold volume up and down plus side key together will take your to download mode don't plug in USB cable
Click to expand...
Click to collapse
you can't enter download mode without plugging in an USB cable...
my best suggestion is to try to go on download mode and reflash the software using the NAND erase function (refer to my post https://forum.xda-developers.com/t/...ts-functions-explained-noob-friendly.4540331/ )
if you don't succeed, search up "Test Point a32 5g"
Bro, I had the same problem, but mine got bricked when updating via Smart Switch( PC ). The app said it was a new firmware version to be updated, I thought: "Oh, nice, let's update it!", but, bro, it was bad thing, it got a error that something went wrong in the update, so, it was not starting;
Couple of things to know:
The Knox will just get tripped if you flash another recovery, eg: TWRP; to root you need a custom recovery, then we can say that root trips the Knox;
My A326B was OEM LOCKED, and there is no way to unlock it when you don't have access perfectly to android visually saying, you can relax about you data because the encryption of Knox does a good job on protecting your files;
When I tried flashing normally it got the message of failure to write in download mode and so in ODIN as well.
Before doing that consider going to a Samsung Support. Or just ignore this message.
After trying many methods, in case you have some problems in entering the bootloader mode, you can use the "Samsung 300K Tool.exe", it helped me entering my A326B to bootloader mode. After doing many stuff, and many times trying to install the system again, I realized because of the text saying about the bootloader, so a downloaded the exact same version of the firmware, in my case, from Brazil, and I just put in ODIN one file, the BL one, that is, the bootloader one. I got surprised when my smartphone just had awaken from a long journey of trying to relive it and I got impressed, even if all that messy things a tested my data was intact, so, my smartphone booted up working perfectly.
Where to find the firmwares? https://www.sammobile.com/firmwares/
if not, just copy the name of the firmware search it on internet, find somewhere to download.
Try to remember what was the last version( month ) that was installed before the installation or the one that was getting installed.
There's is also a windows app( FRP HIJACKER clicking in softbrick fixer choosing some model there) that can unbrick, or even try, or make you little more towards the door of getting out of this problem. Unfortunately, I could not notice, I was worried that time trying to relive the smartphone and so I don't know if by using this app will trip the Knox.
There's something you must know, I don't know where, when your smartphone got interrupted in installation, in which part of the installation.
Anything I can help you, i'm here.
I didn't know that time that by flashing a custom recovery would trip the Knox, saddddd, but I've learned more things.
Samsung Health, Samsung Pass, Samsung Pay, Samsung Secure Folder, and other apps that use Knox Security Technology will not work if Knox get tripped, and It seems like that google pay don't work with in rooted in this smartphone, even if you use Magisk Zygote.
I said bootloader mode in the post, but it was downloader mode.
Samsung just won't update this guy( A326B ) to Android 14.