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.....??
Related
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Does QHSUSB_DLOAD appear in device manager?
I looked up d device manager could not find anything like this. Anywhere specific I need to look at ?
sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Your description is confusing to me. Your thread title says it is softbricked but then you say that you put the phone in debug mode? Does your rom boot fully?
Are you trying to toolkit from the Rom, bootloader or fastboot?
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
I had an issue with softbricking my phone. A good last resort is to flash the RUU (thats what i was told to do and it worked like a charm). It will totally reset your phone to factory settings...and you will need to re-lock your bootloader (just use the All-In-One Toolkit) but besides that, you will once again have a working phone and can just re-root it. If you need the RUU file I can supply the link to it with a little bit of searching. Good Luck!
sadrulez said:
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
Click to expand...
Click to collapse
Everyone's so ready to have a guy run a RUU. Even if he did that it he still would be stuck.
If the toolkit isn't working then you have done something wrong.
Check in device manager and look if you see a category that says "android usb devices"
{
"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"
}
If it's not there you don't have the driver installed correctly. If it is there, double check that you have developer options enabled. In the develop options menu check for something that say enable android debugging.
While you phone is booted normally, plug it into your computer. Can you see something in the notification area that says something about debugging mode?
If you got all that done is the toolkit still not working?
I recommend using a Windows 7 PC to install HTC Sync, then copying the folder to your computer. Then install the drivers manually through device manager, selecting the previous folder that you copied. The drivers should detect your phone then.
@dc211 I can't believe your still using XP lol
Sent from my HTC One S using Tapatalk 2
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
sadrulez said:
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
Click to expand...
Click to collapse
Try holding volume down and power. Out should boot into the bootloader.
Sent from my HTC One S using Tapatalk 2
I already tried that. Holding vol button down + power button restarts the phone in CWM recovery mode
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
sadrulez said:
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
Click to expand...
Click to collapse
Run an RUU, whichever suits your CID /bootloader version.
Sent from my HTC One S using Tapatalk 2
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
Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers
Good news, i got ADB working.
What should i do?
Rgds !
Cheered to soon, seems like all the ADB commands do not work, see ataached image.
ADB devices show a device and when i unplug it it doesnt show a device.
Funny the device name is 12345789ABCDE.....
Any ideas someone ?
{
"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"
}
Nobody knows an answer ?
martyzzz said:
Nobody knows an answer ?
Click to expand...
Click to collapse
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.
cmendonc2 said:
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.
Click to expand...
Click to collapse
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds
martyzzz said:
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds
Click to expand...
Click to collapse
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.
graphdarnell said:
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.
Click to expand...
Click to collapse
Thanks for your reply, i will give it 1 more go before i trash the TF300.
BTW i did use TWRP 2.6.X.X-4.2 i just wasnt able to flash a working rom with it, tried several but no dice...
Ill get back when i have tried.
Again thanks
martyzzz said:
Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers
Click to expand...
Click to collapse
Have you tried this, saved my bricked tab. Thought I was going to have to geta new motherboard at first...
How to unbrick TF300T
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.
hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution
ntamvakeras said:
hi i flashed j3 2017 with odin.the final result was passed but the phone dont boot.it goes only to odin download mode. any solution
Click to expand...
Click to collapse
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!
BigZ1 said:
Well, I'm no expert on booting, but I would try this. First, pull the battery to shut off the phone. Second, reinstall the battery and Press and hold "Volume Up+Home+Power" buttons at the same time till your phone is on,then your Samsung will enter Recovery Mode. It takes a while to get to the recovery screen so be patient. You may see the dead android for a while, but after a few minutes you will get the recovery menu. From there you can try reboot system and see if it will boot for you.
Good Luck!
Click to expand...
Click to collapse
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks
BigZ1 said:
Forgot to ask you a question. I have a J3 that I'm trying to unlock the boot loader. If you get yours working, would you mind checking your developer options to see if you have the button for OEM unlocking? I would appreciate it. Thanks
Click to expand...
Click to collapse
I did that but nothing is happening. Only volume down home end power combination works
{
"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"
}
Did you hold the keys down continuously? That is to say, until you either get recovery mode (or in your case bootloader mode)? If you let go of the key combo after seeing the Samsung J3 screen, you let go too soon. I've always had success with getting into recovery that way. Try it again.
If you truly can't start up in recovery mode, I think you may have wiped out your recovery partition. I'd suggest you use Odin to flash it again.
I just tried booting into recovery mode and then reboot to system. If you can get to that point, you are home free. If you can't get to recovery mode, I think your best bet is to try to reflash with Odin. Maybe you got a bad download. Consider getting a fresh download and reflashing with Odin.
One more thing you might be able to do. IF you had usb debugging enabled, you could connect the phone to your pc, and issue a fastboot command "fastboot reboot" which would reboot you into the system.
This reqires some level of technical skill and some setup work to get fastboot installed (on windows) or if you have a Linux computer, fastboot is probably already installed.
The above is only going to work if you had the developers option for usb debugging turned on before you flashed the phone, and even then it may or may not work, depending on how far the phone gets while booting.
I think at this point, your best option is downloading a fresh copy of your system image from Samsung, and reflashing it with Odin. Hoperfully it will still connect to Odin, since it's already in bootloader mode.
This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green screen
ntamvakeras said:
This phone was fully functional but had broken screen as you see. I left it and I ordered a new from aliexpress. After one month the new screen came. I took the phone for charging but it gave a signal that battery not charged. And the phone not opened. I placed a new battery for charging but still couldn't get to menu and I did a wipe data factory reset but nothing happened so I decided to flash it with odin but while the flash is OK the phone don't boot. When I try to charge it is gives a green scree
Click to expand...
Click to collapse
After you flashed it, and rebooted the phone, how long did you wait for the phone to boot into system? It takes a long time (like maybe 15 minutes) for it to get to the point where you do the initial configuration. If you can try flashing with Odin again, give it at least 15 minutes to get through it's initialization process. That might be what went wrong. Just a guess on my part, but that's what I think. Let me know if it works.
VID_20220727_202947.mp4
drive.google.com
ntamvakeras said:
VID_20220727_202947.mp4
drive.google.com
Click to expand...
Click to collapse
I did all this but nothing happens I don't see the Samsung logo only a green screen. I upload a video to see what I doing
I wish I could help you. I think you are doing everything right. This problem exceeds my knowledge. Maybe someone else smarter can help you.
OK thanks a lot for your assistance
ntamvakeras said:
OK thanks a lot for your assistance
Click to expand...
Click to collapse
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.
BigZ1 said:
I don't know if you are still trying to fix your phone. If so, you might try experimenting with the ODIN option for reboot after flash. Try turning it off, flash with ODIN, unplug cable, pull battery and re-insert, see if it will boot (be patient, it will be slow). If that doesnt work, pull and reinsert battery, then try to boot into recovery with keys.
Just an idea... might get lucky.
Click to expand...
Click to collapse
I did it but nothing happened. The matter is that the phone don't power on after flash. I don't know what else to do
Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.
ntamvakeras said:
View attachment 5669359
Click to expand...
Click to collapse
Will never boot FRP lock and OEm are On i think a account is hanging to the phone , boot in recovery samsung mode and wipe data factory reset from there , reboot
meric57 said:
Hello ntamvakeras, on the first video I tell you that in option you manipulate in pit. I have an old j3 2017 I managed to install official Firmware and then install TRWP, the J3 cable is the good one I didn't have the good is we change it worked.
When you use in option pit these why you do this, I flash I don't touch pit.
Click to expand...
Click to collapse
HI I did that because I have done a lot of experiments in this phone. I know that is wrong but I did that as last way to recover the phone